The pdlogunld command unloads a specified file group to a specified output destination file and places the file group in unload completed status.
HiRDB administrator
pdlogunld -d sys [-s server-name] -g file-group-name |
pdlogunld -d sys -s server-name [-u unit-identifier] -g file-group-name |
Specifies that a system log file is to be unloaded.
Specifies the name of the server corresponding to the file group.
Specifies the name of the file group containing the file to be unloaded.
Specifies the name of the unload log file at the destination. This file is created in the host containing the server whose name is specified in the -s option. When this option is omitted, the standard output is assumed.
If you specify -k hirdb, specify the name of the destination file in the format HiRDB-file-system-area-name/HiRDB-file-name.
Specifies that the unload waiting status is to be retained without changing the file group status. When this option is specified, multiple unload files can be created, because the same generation of files can be unloaded one after another.
Specifies that the file is to be unloaded without checking the file group status. Specifying this option enables the current file group or an unload-completed file group to be unloaded. In this case, the status of the file group remains unchanged.
If the -o option is specified, this option specifies the type of unload log file at the destination. When this option is omitted, the system assumes regular.
When you specify -k regular, you must have already created in advance a directory for storing the unload log files. Also, the read, write, and execution privileges must have been granted to the HiRDB administrator who will be creating that directory.
Before you specify -k hirdb, you must have already used the pdfmkfs command (with -k UTL specified) to create a HiRDB file system area.
If you are using the system switchover facility, make sure that the system log files are unloaded on the disk (character special file) shared by the running system and the standby system. In this case, you can use the unload log files collected by the running system to recover the standby system.
If you specified -k hirdb, use this option to specify the destination file's initial size and extension size (used when the initial size is exceeded) in megabytes (MB).
When this option is omitted, the system assumes the value shown below:
-i option value | Size of system log file | |
---|---|---|
Less than 2,400 MB | 2,400 MB or greater | |
Initial size of destination file | 100 MB | Size of system log file ![]() |
Extension size | 100 MB | (Size of system log file - initial size of destination file) ![]() |
When the standby-less system switchover (effects distributed) facility is used, specifies the unit identifier of the host that contains the disk on which the system log file to be unloaded was created.
When the applicable server and system manager are running, the -u option is ignored, if specified.
Specifying the -u option results in an error if any of the following is true:
The following table describes whether or not the -u option is required:
Server status | Host containing the disk where file is created | Specification of -u option |
---|---|---|
Active | Host containing the running back-end server | Optional |
Inactive | Host containing the primary back-end server | |
Other host | Mandatory |
Record length of unload log file (bytes) | Sector length of the HiRDB file system area used during pdfrstr command execution (bytes) | ||
---|---|---|---|
1,024 | 2,048 | 4,096 | |
1,024 | Y | N | N |
2,048 | Y | Y | N |
4,096 | Y | Y | Y |