Check the KFPS01160-E or KFPS01162-W message to identify the server that has insufficient free area. If an error occurred with the pdlogcls command, the server specified by this command is the affected server.

Handling level 2 limits

This server is in a status in which new transactions can no longer be scheduled. The HiRDB administrator can execute the pdls -d svr command to determine the server that is in this status. The STATUS entry in the command's execution results shows TRNPAUSE for the server that is in scheduling suppression status.

Execute the pdlogls command on the system log files at the applicable server to determine their status.

Perform the tasks listed below to increase the number of system log files in swappable target status:

• If there are reserved files, place them in swappable target status.
• If there are files in unload wait status, place them in unload completed status.
• If there are files in extracting status, place them in extraction completed status.
• If there are files in overwriting denied status for online reorganization, place them in overwriting permitted status for online reorganization.

Refer to the KFPS00993-I message to check the transactions that were forcibly terminated. The REQUEST entry in this message shows log_remain_check for transactions that were forcibly terminated. Once the KFPS01161-I message is output, scheduling of new transactions has resumed, and the forcibly terminated transactions must be re-executed.

The KFPS01163-W message is output if there are transactions that are not subject to forced termination. HiRDB waits for the processing by these transactions to terminate. Do not use a command such as pdcancel to forcibly terminate these transactions, because this might cause error shutdowns in RDAREAs.

You can use the following procedure to identify the UAPs, operation commands, and utilities that issued transactions that continue to operate.

Procedure

1. Refer to the KFPS01160-E or KFPS01163-W message to identify the name of the affected server.
2. Use the pdls -d trn -a -s server-name command to acquire the required transaction information. In -s server-name, specify the server name identified in 1.
3. Refer to PROGRAM or C-PID in the command execution results to identify the UAP, operation command, or utility that issued a transaction.

Use the status information file for system log files to identify the cause of the area insufficiency for system log files. For details, see 3.9.6 Output of status information file for system log files (function for monitoring the free area).

If the function for monitoring the free area for system log files activates more than once, there might be a defect in the design of the system log files (such as the number of files or the file size). In this case, revise the design of the system log files. For details about designing system log files, see the HiRDB Version 9 Installation and Design Guide.

If the pdlogswap command is used to swap system log files while the percentage of free area is less than the warning value, HiRDB is more likely to terminate forcibly because there are no files in swappable target status. Therefore, do not execute the pdlogswap command at such times.