The MovePartition action moves the specified partition to the specified location.
If the destination of the move is on the same physical device as the source, the move is accomplished via a file system move (or rename). In this scenario, access to the file is blocked for the duration of the rename and meta-data updates. If the destination is on a different physical device, the move is accomplished using a backup copy and verify followed by removal of the source file.
When a non-frozen partition is moved to a different physical device, the MovePartition action blocks new transactions, acquires a database quiet point, and freezes the partition for the duration of the operation; transactions are unblocked after the partition has been transitioned to a frozen state. The quiet point is required to ensure there are no updates to the partition in the pipeline that would require an undo action should a transaction abort. Moving a partition required for object creation (any partition in the creation window) is prohibited.
The syntax of the MovePartition action is as follows.
jdbadmin action=MovePartition
[path=database-path]
[ini=initialization-file-name]
[server=multiUser|singleUser]
file=file-name part=partition-ID
location=file-directory
The path parameter is optional in multiuser mode.
The required file and part parameters specify the target file partition.
The required location parameter specifies the target path.