pdlogrm (Delete log file)

Function

The pdlogrm command deletes a log physical file from the HiRDB file system. An open physical file cannot be deleted.

Executor

HiRDB administrator

Format

HiRDB/Single Server

pdlogrm -d sys|spd [-s server-name] -f physical-filename [-u]

HiRDB/Parallel Server

pdlogrm -d sys | spd -s server-name [-X unit-identifier] -f physical-filename [-u] [-D]

Options

Specifies the type of log file to be deleted:

sys
System log file
spd
Synchronization point dump file

Specifies the name of the server corresponding to the file group that consists of the physical file.

Specifies the absolute pathname of the physical file to be deleted. The physical file name must be specified in the format HiRDB-file-system-area-name/HiRDB-filename.

If you use Real Time SAN Replication based on the log-only synchronous method, the file to be deleted depends on the site where the command is executed.

Specifies that if the physical file specified with the -f option is a system log file, it is to be deleted forcibly even if it is in any of the following statuses:

When this option is omitted, the system checks the unload status of the physical file; if the file is in unload wait status, the command results in an error.

This option is ignored if specified for a synchronization point dump file.

This option is used when normal deletion processing (pdlogrm command with -u not specified) cannot be executed for some reason. If the file still cannot be deleted by the pdlogrm command with -u specified, the pdfrm command can be used.

When the standby-less system switchover (effects distributed) facility is used, specifies the unit identifier of the host that contains the disk from which the file is to be deleted.

When the applicable server is running, the -X option is ignored, if specified.

Specifying the -X option results in an error if any of the following is true:

The following table describes whether or not the -X option is required:

Server statusHost containing the disk where file is createdSpecification of -X option
ActiveHost containing the running back-end serverOptional
InactiveHost containing the primary back-end server
Other hostMandatory

Specifies that a unit or server is to be deleted by the pdchgconf command.

To delete a unit or server, the system deletes that unit's or server's system log files and synchronization point dump files. When this option is specified, the command will not check the server name.

If you are executing the pdlogrm command with this option specified, make sure that the command is executed at the unit that contains the system log files or synchronization point dump files to be deleted.

Rules

  1. The pdlogrm command can be executed at any time, whether or not HiRDB is active (except during HiRDB startup or termination processing).
  2. The pdlogrm command must be executed at the server machine containing the single server or the server machine where the system manager is located.

Note

  1. The result of the pdlogrm command can be determined from the command's return code or error message, if any. The return codes are as follows:
    0: Normal termination
    4: Abnormal termination
    8: Abnormal termination (such as invalid option or rsh error)
    12: Abnormal termination (when retry was executed from a standby system in a configuration in which IP addresses are not inherited)
  2. If you are using Real Time SAN Replication based on the log-only synchronous method, and log application processing has not been performed on the system log file that is to be deleted, when you delete the system log file at the transaction execution site the log application processing will terminate abnormally because of detection of missing log information at the log application site. In such a case, you must perform the preparations for log application and restart the log application processing.
    For details about the preparations for log application, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide.