22.10 Audit trail file error handling

Organization of this section
(1) When an error occurs in an audit trail file
(2) When an error occurs in the HiRDB file system area used for audit trail files (when all audit trail files are in shutdown status)
(3) When HiRDB is terminated forcibly because there are no swappable target audit trail files

(1) When an error occurs in an audit trail file

When an error occurs in an audit trail file, the file is placed in shutdown status. An audit trail file in shutdown status cannot be used except to be deleted. Take action according to the following procedure:

Procedure
  1. Identify the audit trail file in shutdown status from the KFPS05704-E message.
    You can use the pdls -d aud command to identify the generation in which the error occurred. If HiRDB is running, the auditor executes the pdls -d aud command.
  2. Use the pdaudrm command to delete the audit trail files in shutdown status. To delete forcibly the files in data load waiting status, specify the -f option.

Files in shutdown status cannot be data loaded. Therefore, if they are not data loaded, the entire audit trail will be lost.

(2) When an error occurs in the HiRDB file system area used for audit trail files (when all audit trail files are in shutdown status)

This explains the procedure when an error has occurred in the HiRDB file system area used for audit trail files, causing all audit trail files to be placed in shutdown status.

The HiRDB processing depends on the value of the pd_aud_no_standby_file_opr operand. If down is specified, HiRDB (or unit for a HiRDB/Parallel Server) is terminated forcibly. If forcewrite (default) is specified, audit trail output stops, but HiRDB continues in operation. The HiRDB administrator uses the procedure explained below.

Procedure
  1. If HiRDB is operating, use the pdstop command to terminate HiRDB normally. If normal termination is not possible, use the pdstop -f command to terminate HiRDB forcibly.
  2. Use the pdfmkfs command to re-create the file system area for audit trail files. If the HiRDB file system area cannot be used due to a fault such as s disk error, create another HiRDB file system area for audit trail files on a different disk.
  3. If you changed the file system area for the audit trail files, also change the specification of the pd_aud_file_name operand.
  4. If there is a backup of the file system area for audit trail files, use the pdfrstr command to recover the HiRDB file system area.
  5. Use the pdstart command to start HiRDB.

(3) When HiRDB is terminated forcibly because there are no swappable target audit trail files

If down is specified in the pd_aud_no_standby_file_opr operand and only one swappable file remains, terminate HiRDB forcibly (for a HiRDB/Parallel Server, terminate the unit). The HiRDB administrator uses the procedure explained below.

(a) For a HiRDB/Single Server

Select one of the following procedures:

Procedure 1: When pd_aud_max_generation_num < 200
  1. Specify 200 for the pd_aud_max_generation_num operand.
  2. Use the pdstart command to start HiRDB.
  3. Use the pdload command to data load the files in data load waiting status.
Procedure 2: When pd_aud_max_generation_num = 200
  1. Specify N in the pd_audit operand.
  2. Use the pdstart command to start HiRDB.
  3. Use the pdload command to data load the files in data load waiting status.
  4. Use the pdaudbegin command to start collection of the audit trail.
(b) For a HiRDB/Parallel Server

Select one of the following procedures:

Procedure 1: When pd_aud_max_generation_num < 200
  1. Use the pdstop -f command to terminate HiRDB forcibly.
  2. Specify 200 for the pd_aud_max_generation_num operand.
  3. Use the pdstart command to start HiRDB.
  4. Use the pdload command to data load the files in data load waiting status.
Procedure 2: When pd_aud_max_generation_num = 200
  1. Use the pdstop -f command to forcibly terminate HiRDB.
  2. Specify N in the pd_audit operand.
  3. Use the pdstart command to start HiRDB.
  4. Use the pdload command to data load the files in data load waiting status.
  5. Use the pdaudbegin command to start collection of the audit trail.