2. Using Ingres Commands : logstat Command—Display Logging Status : Logstat Command Output – List of Transactions
 
Share this page                  
Logstat Command Output – List of Transactions
The List of Transactions provides statistical information on each active transaction. This section has the following fields:
Tx_id
Identifies the transaction ID used by the logging system
Tran_id
Identifies the transaction. The transaction ID is used by both the logging and locking systems. The ID is useful when you want to follow a transaction from lockstat to logstat output.
Database
Identifies the ID of the database. This ID is the same as the ID in the List of active databases section of the logstat output.
Process
Indicates the ID of the process currently working on this transaction. This field corresponds to the internal logging system ID in the List of active processes section of logstat.
Dis_tran_id
Currently not used
Session
Indicates the user session ID that owns this transaction. This is the same ID used in iimonitor output. Use this ID to locate the user and the terminal that initiated the transaction.
First
Indicates the log file address of the first record associated with this transaction
Last
Indicates the log file address of the last record associated with this transaction
Cp
Indicates the first consistency point address taken that concerns this transaction
FirstLSN
Indicates the log sequence number associated with the first record written to the log file by this transaction
LastLSN
Indicates the log sequence number associated with the last record written to the log file by this transaction
WaitLSN
Indicates the log sequence number that must be written to the log before the transaction can proceed
Write
Indicates the number of log buffer writes because of this transaction
Split
Indicates the number of times this transaction had to wait for a log buffer in order to write a log record that spanned multiple buffers
Force
Indicates the number of times the log buffer was flushed. The force conditions are commented in more detail under the Log forces field in the Summary section above.
Wait
Indicates the number of times this transaction had to wait for a logging system-related event
Reserved
Indicates the number of log blocks reserved by this transaction for recovery operations
WaitBuf
Indicates the log buffer on which the transaction is waiting to be written to the log
Status
Indicates the status of this transaction. This field can take the following values:
ACTIVE—this transaction has written a number of records to the log file.
INACTIVE—this transaction is in the retrieve mode and has not written any records to the log file.
PROTECT—this transaction is a user transaction (as opposed to an internal system transaction) and will be recovered in the event of a server or system failure.
JOURNAL—this transaction must be journaled. This flag indicates that the transaction should be archived.
Wait Reason
Indicates why the transaction is waiting. Wait Reason can have the following values:
(not waiting)—The transaction is not waiting.
FORCE—waiting for a log force
FREE—waiting for a free log buffer
SPLIT—waiting for a log split completion
HDRIO—waiting for log header I/O completion
CKPDB—waiting for a ckpdb completion
OPENDB—waiting for an open database completion
BCPSTALL—waiting for BCP log write to complete
LOGFULL—waiting because of LOGFULL condition
FREEBUF—waiting for a free buffer
LASTBUF—waiting for the last buffer in the transaction to be written
BUFIO—waiting for a log buffer to be freed
EVENT—waiting for a log event
ABSOLUTE_LOGFULL—waiting at the absolute end of a LOGFULL condition
WRITEIO—log_writer thread specific; the logwriter is idle
User
Indicates the owner of this transaction. User can have the following values:
logfile_I/O_thread—log file read/write thread
group_commit_thread—group commit thread
buffer_manager—the buffer manager
log_reader_transaction—log file read/write thread
recovery_thread—the DMFRCP recovery thread
consistency_pt_thread—the consistency point thread
consistency_point_timer—the consistency point timer thread
write_behind—the write behind thread
security audit thread—in C2 enabled systems only, the security audit thread
username—user session