HiRDB uses two message log files (pdlog1 and pdlog2) alternately. When one message log file becomes full, HiRDB stops writing messages to that file and starts writing messages to the other file. When this occurs, existing messages in the latter file are erased.

The following figure shows message log file swapping.

Figure 8-1 Message log file swapping

Explanation

When the pdlog1 message log file becomes full, the message log output destination is switched to pdlog2. When this occurs, existing messages in pdlog2 are erased.

Reference note

• To determine which message log file is the current file, use the OS's ls command to check the date and time of the most recent update in each file. The file with the most recent update date and time is the current message log file.
• Message log files are not swapped at the time of HiRDB startup (all startup modes). Messages continue to be output to the message log file that was the output destination when HiRDB was previously terminated.

• Action to be taken by the HiRDB administrator when message log files are swapped
  When the message log files are swapped, the KFPS01910-I message is output to the message log file that is about to be swapped. To save the message logs in the message log file that is about to be swapped, you must make a backup of that message log file.
  
• Changing the message log file size
  You use the pd_mlg_file_size operand to specify the message log file size. Change the size as needed.