The changeFilePaths command changes the backup path attribute and the database path attribute of a file or a file partition in the backupinfo file. A JADE database backup is a disk backup and is described by a backupinfo file that contains information about all database files. A file or file partition has a backup path attribute describing its location within the disk backup (used by verifyChecksums and restore operations), and a database path attribute containing its database path specification as copied from the database control file (used by the restore operation). By default:
Database files are located in the same directory as the database control file (_control.dat)
Database file partitions by default are located in the same directory as the partition control file (file-name.dat)
Backup files are located in the same directory as the backup control file (backupinfo)
Backup file partitions are located in the same directory as the backed-up partition control file
When backing up a database, it can be necessary to specify some non-default file or file partition backup paths; for example, when some files or file partitions are too big for the default location. When absolute paths are specified, that backup can be placed only on a machine that has devices matching the path specifications, and the files and file partitions with non-default backup paths have to be correctly placed to reconstitute the disk backup; otherwise the verifyChecksums and restore operations will fail.
Similarly, for operational reasons, a live database can have some non-default file or file partition database paths in use. When absolute paths are used, a backup of that database can be restored only on a machine that has devices matching the path specifications; otherwise the restore operation will fail.
The syntax of the changeFilePaths command in the jdbutilb command line is as follows.
jdbutilb changeFilePaths file-name
backupinfoPath=directory
ini=initialization-file-name
[part=partition-id]
[newBackupPath=directory|<default>]
[newDatabasePath=directory|<default>]
[nostatus]
The path argument is not used by this command, so it need not be specified. You can specify one or both of the newBackupPath and the newDatabasePath arguments.
The value of the newBackupPath argument is checked for validity and must exist (as it is where the file is located). The value of the newDatabasePath argument is checked for validity only if it is absolute, but it does not have to exist (the restore operation will create it, if necessary).
You can specify a file-name of * (the asterisk symbol), to cause the arguments to be applied to all files and partitions in the backupinfo file. For example, setting newDatabasePath="<default>" and then restoring the database would result in the same outcome for that restored database as specifying the clearFilePaths argument in the restore command.