See Determining the size of system log files in the HiRDB Version 9 Installation and Design Guide to revise the estimated system log file size.

If the revised estimate shows that the system log files that were added are not needed, delete them. For details about how to delete these files, see 20.17.8 Deleting the system log files that were added.

If the cause of the system log file shortage is known, implement the revision or action explained in the table below. If the problem is not due to the size of the system log file, make sure that a system log file shortage will not occur due to a factor other than the system log file size.

Table 20-23 Causes of system log file shortage, and revision or action required

No.	Cause of system log file shortage	Description of revision or action
1	Because the automatic log unloading facility stopped, the number of files waiting to be unloaded increased, causing a system log file shortage.	See 3.8 Using the automatic log unloading facility and revise the settings for the automatic log unloading facility.
2	Because system log files were not unloaded or their status was not changed, the number of files waiting to be unloaded increased, causing a system log file shortage.	Take one of the following actions: Consider using the automatic log unloading facility. For details, see 3.8 Using the automatic log unloading facility. Revise the system log file size. See Determining the size of system log files in the HiRDB Version 9 Installation and Design Guide.
3	Because transactions were not committed for a long time, the number of files that are overwrite disabled increased, causing a system log file shortage.	Take one of the following actions: Revise the transaction that caused the problem. Revise the system log file size. See Determining the size of system log files in the HiRDB Version 9 Installation and Design Guide.
4	Because synchronization point dump validation processing was skipped, the number of files that are overwrite disabled increased, causing a system log file shortage.	See 23.3 Tuning the synchronization point processing time when deferred write processing is used and revise the synchronization point processing time.
5	Because an error occurred in a system log file, there was no file that could be made a swappable target, and this caused a system log file shortage.	Investigate the cause of the error that occurred in the system log file and take the necessary action.
6	Because the system log extraction process fell behind during linkage with HiRDB Datareplicator, the number of files in extracting status increased, causing a system log file shortage.	See the HiRDB Datareplicator error message that is output, identify the reason why the system log extraction process fell behind, and take the necessary action. As a guideline, always keep the number of files in extracting status at 3/4 or less of the total.
7	During updatable online reorganization, the number of files in overwriting denied status for online reorganization increased, causing a system log file shortage.	See Determining the size of system log files in the HiRDB Version 9 Staticizer Option Description and User's Guide, and revise the size of the system log files that are needed during updatable online reorganization.

When the cause of a system log file shortage cannot be determined

Check whether any of the messages listed below were output before the unit terminated abnormally due to a system log file shortage. The output message can be used to identify the cause.

• KFPS01150-E message
  This message is output when the automatic log unloading facility stops. Make the revision prescribed for No. 1 in the table above.
  
• KFPS01202-E message
  This message is output when an error occurs in a system log file. Make the revision prescribed for No. 5 in the table above.
  
• KFPS02179-I message
  This message is output when synchronization point dump validation processing is skipped. If the KFPS02179-I message is output many times, take the action prescribed in the message.