Determining if transactions are being captured for replication
Review log capture activity at the current node in an Enterprise Replication (ER) domain.
On the menu of the HCL OpenAdmin Tool (OAT) for Informix®, click . Review the capture state and the log position fields. The progress that these fields show might help you determine if transactions are being actively captured.
| Fields | Description |
|---|---|
| Capture State | The state of log capture at the current node: Running, Down, or Uninitialized. |
| Current Log Position | The logical log position of the current transaction. |
| Capture Log Position | The logical log position at which transactions are being captured for replication. Compare capture log position to the current log position to determine if ER is keeping up with transactions. |
| Replay Log Position | The point from which ER starts rereading the
log information in to the log update buffers after a failure. All
the transactions generated before this position at all the target
servers have been applied by ER or stored in the stable queue space. Important: To prevent loss of data, ensure that the log replay
position is never overwritten. If the replay position is not advancing,
the queue might be full or a remote node might be down.
|