This section explains the action to take when there are system log files that are in extracting status.

• If HiRDB Datareplicator is extracting system logs
  Wait for the files in extracting status to be completely extracted.
  
• If system log extraction was halted due to abnormal termination of HiRDB Datareplicator
  Restart HiRDB Datareplicator to resume system log extraction. For details about the procedure, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
  

The following uses an example to explain the method of identifying the system log files that are in extracting status while the unit is stopped.

Example

The unit terminated abnormally due to a system log file shortage at the back-end server (bes1) while HiRDB Datareplicator was linked. This example identifies the system log files that are in extracting status on bes1.

Procedure

1. Execute the pdls command to identify the system log files being extracted.
   

   

   In this example, system log file log004 is being extracted.
   
2. Execute the pdlogls command to identify the system log files that are in extracting status.
   

   

   From the execution results of the pdls and pdlogls commands, identify system log files that are in extraction completed status. System log file log003, which has a smaller generation number than system log file log004 (identified in step 1 as being extracted), is in extraction completed status.
   Since system log files with a different Run ID from log004 were being used before log004, log001 and log002 are also in extraction completed status.