A. Command Reference : relocatedb Command--Move Location to Another Location
 
Share this page                  
relocatedb Command--Move Location to Another Location
The relocatedb command moves the journal, dump, checkpoint, or default work location for a database to another location (when a disk fills or is swapped out, for example).
The relocatedb command has the following format:
relocatedb dbname[/server_class] -new_ckp_location=locationname |
-new_dump_location=locationname | -new_jnl_location=locationname |
-new_work_location=locationname
dbname
Specifies the name of the database whose files are to be moved, and if required, the server_class, as described in Standard Flags and Parameters.
-new_ckp_location=locationname
Specifies the name of the new checkpoint location. The location must be defined with checkpoint usage. Checkpoints should not be run when relocating a checkpoint location.
VectorH: If the old location is II_CHECKPOINT, and the new location is HDFS, the format of the checkpoints is incompatible, and you must first move or delete the files at the old checkpoint location. If the old checkpoint location is HDFS, the new checkpoint location must be HDFS.
-new_dump_location=locationname
Specifies the name of the new dump location. The location must be defined with dump usage. Checkpoints should not be run when relocating a dump location.
-new_jnl_location=locationname
Specifies the name of the new journal location. The location must be defined with journal usage. Journaling and checkpoints should not be run when relocating a journal location.
-new_work_location=locationname
Specifies the name of the new work location. The database must have been previously extended to this location for work usage. An exclusive lock is required during the relocation operation.