The following table explains the conditions under which audit trail files are swapped.

Table 24-18 Conditions under which audit trail files are swapped

Condition for swapping	Explanation
File is full.	When the output audit trail becomes full, the file is swapped. The size of an audit trail file is specified in the pd_aud_max_generation_size operand.
Error in the current file.	If an error occurs during I/O processing to the current file, the file is swapped.
pdaudswap command is executed.	When the pdaudswap command is executed, the file is swapped.
HiRDB is restarted.	When HiRDB (or unit for a HiRDB parallel server configuration) is restarted, the file is swapped. In the case of normal startup or a restart after planned termination, the file is not swapped and the file that was the current file at the time of the previous HiRDB termination continues to be used.

In the following cases, the file that should be swapped in is replaced automatically by another file:

• Generation of the audit trail file that was to be the swap target failed
• Update to the management information failed

The processing depends on whether the number of audit trail files used has reached the maximum (value of pd_aud_max_generation_num).

• If the number of audit trail files has not reached the maximum (value of pd_aud_max_generation_num), another audit trail file is created, and that file becomes the swap target. The smallest unused generation number is allocated as the file generation number.
• If the number of audit trail files has reached the maximum number (value of pd_aud_max_generation_num), the data load completed file (excluding files in shut down status) with the oldest update date becomes the swap target.

When there is no file that can be used as the swap target, HiRDB acts according to the value specified for the pd_aud_no_standby_file_opr operand.

If forcewrite (the default) is specified

The following table shows HiRDB's actions when there is no swappable audit trail file, and the actions the auditor must take:

Condition for swapping	HiRDB's action	Action to be taken
File is full. Error in the current file. HiRDB is restarted.	Outputs the KFPS05706-W message and forcibly swaps to the audit trail file waiting for data load (excluding files in shutdown status). In this case, the audit trail file waiting for data load that has the oldest update date is made the swap target.	--
pdaudswap command is executed.	Outputs the KFPS05752-E message (reason code: NO_STANDBY_FILE) and causes a command error. In this case, HiRDB (or the unit, for a HiRDB parallel server configuration) remains active.	The auditor must load the data from the audit trail file to the audit trail table and place the swap target audit trail file in data loaded status.

Legend:

--: Not applicable

If down is specified

The following table shows HiRDB's actions when there is only one remaining swappable audit trail file, and the actions the auditor must take:

Condition for swapping	HiRDB's action	Action to be taken
File is full. Error in the current file.	Outputs the KFPS05705-E message and forcibly terminates HiRDB (or the unit, for a HiRDB parallel server configuration).	See 24.10(3) When HiRDB is terminated forcibly because there are no swappable target audit trail files and take the appropriate action.
pdaudswap command is executed.	Outputs the KFPS05752-E message (reason code: NO_STANDBY_FILE) and causes a command error. In this case, HiRDB (or the unit, for a HiRDB parallel server configuration) remains active.	The auditor must load the data from the audit trail file to the audit trail table and place the swap target audit trail file in data loaded status.
HiRDB is restarted.	If there is a swappable audit trail file Restarts HiRDB (or the unit, for a HiRDB parallel server configuration).
	If there is no swappable audit trail file Outputs the KFPS05724-E and KFPS05725-W messages, stopping the security audit facility, and then restarts HiRDB (or the unit, for a HiRDB parallel server configuration).	The auditor must load the data from the audit trail file to the audit trail table. Then, the HiRDB administrator must use the pdaudbegin command to restart the security audit facility.

By specifying the pd_aud_file_wrn_pnt operand, you can output a warning message (KFPS05123-W message) when the number of unswappable audit trail files reaches the warning value. If the warning message is output, load the data from the audit trail file to the audit trail table as soon as possible.