The SetPartitionLocation action changes the default or designated physical location of the specified offline file partition. The location argument for this action specifies the file system directory in which the offline partition will be located when it is marked online. The value of the location attribute is stored in the parent partition control file and is similar in function to the path attribute for map files, which is stored in the global database control file. If the location of a partition has never been set, it defaults to null; a value of null means that it is located in the directory of the parent partition control file. Relative paths are assumed to be relative to the database path.
The purpose of the SetPartitionLocation argument is to cause the database to open the file in the specified location. When the location is changed, the actual partition file must be in that location before it is marked online. A typical usage would be to allow offline partitions that have been burned to optical media to be mounted in a different file system directory (for example, a different drive).
The syntax of the SetPartitionLocation action is as follows.
jdbadmin action=SetPartitionLocation
[path=database-path]
[ini=initialization-file-name]
[server=multiUser|singleUser]
file=file-name [part=partition-ID
location=file-directory
The path argument is optional in multiuser mode.
The required file and part arguments specify the target file partition.
The required location argument specifies the file system directory in which the offline partition will be located when it is marked online.