6. Troubleshooting Ingres : Performance Problems : Diagnose DBMS Server Due to Logging System Problem : Logstat Status Fields
 
Share this page                  
Logstat Status Fields
The problem states and resolutions of logstat fields are described in the following table:
Status Field
Description
Action
ONLINE, ECPDONE
A consistency point is completed. The system is fully functional and online.
The logging system has finished a consistency point. This status flag is present most of the time while the logging system is functioning normally. If this is your status, stop this procedure and review Operating System Resources.
LOGFULL
The log file is full.
A status of LOGFULL means that the system is suspended from processing new requests because there is no more room in the transaction log file. It remains so until the problem is corrected. Examine the other status field entries.
If ARCHIVE is also indicated, the Archiver is actively processing the log file to free up space. The LOGFULL condition is removed when the Archiver is finished.
CPNEEDED
A consistency point is needed.
CPNEEDED means the logging system is about to take a consistency point.
ARCHIVE
The Archiver is processing.
The status ARCHIVE means the Archiver process is archiving.
START_ARCHIVER
The Archiver has stopped.
A status of START_ARCHIVER means that the archiver process stopped. Restart the Archiver.
FORCE_ABORT
The force-abort- limit has been reached.
If the status is FORCE_ABORT, a transaction came too close to the end of the transaction log file before the oldest was committed to disk, and reached the force-abort-limit. The oldest open transaction is aborted to free space for the new one.
You can use logstat (or ipm) to monitor the force abort. The system frees the FORCE_ABORT status when the abort operation is completed.
RECOVER
The recovery process is performing recovery.
If the status is RECOVER, the logging system is in recovery, a normal mode. Recovery requires some time because Ingres is optimized to commit rather than back out of transactions.
Important!  If the server is recovering a lengthy transaction, be aware that shutting down the server with iimonitor's "stop server" (or by killing processes at the operating system level) results in slower recovery. Allow the recovery to proceed normally. You can monitor the progress of the recovery with logstat and iimonitor or the ipm utility.
Many other normal states appear on the status line. For additional information on reading logstat output, see the Logstat section in the Command Reference Guide.