Logging (_Logging)
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
The _Logging VST includes before-image and after-image logging information and two-phase commit status.
| Field name | Data type | Description |
|---|---|---|
| _Logging-2PC | CHARACTER | "Yes" indicates that two-phase commit is enabled. "No" indicates that two-phase commit is disabled. |
| _Logging-2PCNickName | CHARACTER | Nickname used to identify the coordinator database. You specify a nickname when you enable two-phase commit. |
| _Logging-2PCPriority | INTEGER | Priority for the coordinator database. You specify the priority when you enable two-phase commit. |
| _Logging-AiBegin | CHARACTER | Date of the last AIMAGE BEGIN command. |
| _Logging-AiBlkSize | INTEGER | Size of the after-image block. You can change the AI block size. This reduces I/O rates on disks that have AI files. |
| _Logging-AiBuffs | INTEGER | Number of buffers in the AI buffer pool. You
can change the number of AI buffers with the After-image Buffers (-aibufs) startup
parameter. The default value is 1. |
| _Logging-AiCurrExt | INTEGER | Current after-image extent. |
| _Logging-AiExtents | INTEGER | Number of AI files or extents. |
| _Logging-AiGenNum | INTEGER | Generation number of the current AI extent. |
| _Logging-AiIO | CHARACTER | After-image I/O. "Reliable" indicates that synchronous or direct I/O is being used for AI writes. "Buffered" indicates that buffered I/O is being used for AI writes. |
| _Logging-AiJournal | CHARACTER | "YES" indicates that after-imaging is enabled; "NO" indicates that after-imaging is disabled. |
| _Logging-AiLogSize | INTEGER | Number of kilobytes in the AI log file, if the AI extent in use is variable length. If the AI extent in use is fixed length, the value is 0. |
| _Logging-AiNew | CHARACTER | Date of the last AIMAGE NEW command. |
| _Logging-AiOpen | CHARACTER | Date when the AI log was last opened. |
| _Logging-AISequence | INT64 | The database AI sequence number (of the current AI file) |
| _Logging-BiBlkSize | INTEGER | BI block size. |
| _Logging-BiBuffs | INTEGER | Number of BI buffers. |
| _Logging-BiBytesFree | INTEGER | Number of free bytes remaining in the current BI cluster. |
| _Logging-BiClAge | INTEGER | Period of time that must pass before a BI cluster is reused. This period ensures that database blocks flushed at checkpoint are moved from the UNIX buffers on disk. When this occurs, the transaction is durably recorded on disk. |
| _Logging-BiClSize | INTEGER | BI cluster size. |
| _Logging-BiExtents | INTEGER | Number of BI extents. |
| _Logging-BiFullBuffs | INTEGER | Number of full BI buffers. |
| _Logging-BiIO | CHARACTER | One of the following: "Reliable" indicates that synchronous or direct I/O is being used for BI writes; "BUFFERED" indicates that buffered I/O is being used for BI writes. |
| _Logging-BiLogSize | INTEGER | Number of kilobytes in the BI file. |
| _Logging-BIClusterHWM | INT64 | The highest cluster ever used |
| _Logging-CommitDelay | INTEGER | Current value of the Delayed BI File Write (-Mf)
parameter. |
| _Logging-CrashProt | INTEGER | "Yes" indicates that crash protection is enabled; "No" indicates that crash protection is disabled. |
| _Logging-CurrBICluster | INT64 | The current BI Cluster |
| _Logging-LastCkp | CHARACTER | Time of the last checkpoint. |