relocatedb Command—Move a Location to a New 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 can also make a copy of an entire database. Any location in the original database can be moved to a new location in the new database.

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 | -new_database=newdbname
[-location=locationname{, locationname} -new_location=locationname
{, 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.

• -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.

• -new_database=newdbname

  Specifies the name of the new database to be created.

  This option creates all the directories and copies all the files from the old database to the new database.

  An exclusive lock on the original database is required while the original database is copied to the new database.

  Note: Files for data recovery (*.ckp, *.jnl, *.dmp) are applicable to the original database only and are not valid for the new database. Following a relocatedb -new_database=newdbname, the new database should have a checkpoint taken with the appropriate journaling flags set according to its usage.

• -location=locationname(, locationname)

  Specifies a list of locations. All locations in the list must be valid locations for the database. The physical files in the data areas are copied to the same location for the new database.

  When new_location is specified, the physical files in each data area in the location list is copied to the corresponding data area in the new location list.

  This option is valid only for database relocation (-new_database=newdbname).

• -new_location=locationname(, locationname)

  Specifies a list of new locations. All locations in the list must be defined for the installation, and the usage must be compatible with the usage of the corresponding area in the location list. Each location in the location list must be mapped to a distinct location in the new location list.

  This option is valid only for database relocation (-new_database=newdbname).

relocatedb Example: Relocate Checkpoint Files

The following command relocates the checkpoint location for the empdata database to newckp:

relocatedb empdata –new_ckp_location=newckp

This command example does the following:

• Performs an update to the iidbdb: update iidatabase.ckpdev='newckp' where name='empdata'. (The update can be verified by connecting to the iidbdb database and doing a select from iidatabase where name='empdata'.)
• Updates the checkpoint location in the configuration file. (This can be verified by examining the output of the infodb empdata command.)
• Copies checkpoint files from the old checkpoint location to the new checkpoint location.
• Deletes checkpoint files from the old checkpoint location.

relocatedb Example: Relocate Journal Files

The following command relocates the journal location for the empdata database to newjnl:

relocatedb empdata –new_jnl_location=newjnl

This command example does the following:

• Performs an update to the iidbdb: update iidatabase.jnldev='newjnl' where name='empdata'. (This can be verified by connecting to the iidbdb database and doing a select from iidatabase where name='empdata'.)
• Updates the journal location in the configuration file. (This can be verified by examining the output of the infodb empdata command.)
• Copies journal files from the old journal location to the new journal location.
• Deletes journal files from the old journal location.

relocatedb Example: Relocate Dump Files

The following command relocates the dump location for the empdata database to newdump:

relocatedb empdata –new_dump_location=newdump

This command example does the following:

• Performs an update to the iidbdb: update iidatabase.dmpdev='newdump' where name='empdata'. (This can be verified by connecting to the iidbdb database and doing a select from iidatabase where name='empdata'.)
• Updates the dump location in the configuration file. (This can be verified by examining the output of the infodb empdata command.)
• Copies dump files from the old dump location to the new dump location.
• Deletes dump files from the old dump location.

relocatedb Example: Relocate the Work Area

The following command relocates the work location for the empdata database to newwork:

relocatedb empdata –new_work_location=newwork

The command above does the following:

• Performs an update to the iidbdb: update iidatabase.sortdev='newwork' where name='empdata'. (This can be verified by connecting to the iidbdb database and doing a select from iidatabase where name='empdata'.)
• Updates the default work location in the configuration file. (This can be verified by examining the output of the infodb empdata command.)
• No files are copied for work locations.

relocatedb Example: Copy Database to a New Database

The following command copies the empdata database to a new database called empdev:

relocatedb empdata –new_database=empdev

This command example does the following:

• Inserts a record in the iidatabase table for this database.
• Inserts a record in the iiextend table for all locations to which the new database is extended.
• Creates all the directories and copies all the files from the old database to the new database.
• Builds a database configuration file for the new database.

After the new database is created, you should be able to connect to it and access all data.