The table below contains the field descriptions of the OpenEdge Replication VST, _ReplAgentActivity.

Table 1. Virtual system table _ReplAgentActivity field description
Field name Field number Data type Description
_ReplAgtAct-AgentID 2 INT64 The ROWID of _Repl-AgentActivity VST record.

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-AgentName 3 CHARACTER The name of the replication agent as configured in the repl.properties file.

Format X(32)

_ReplAgtAct-ConnectTime 4 CHARACTER

The date and time when the replication server successfully connected to the replication agent.

Format X(24)

_ReplAgtAct-BlocksReceived 5 INT64

The number of after-image (AI) blocks that the replication agent has received from the replication server.

Format >>>>>>>>>9

_ReplAgtAct-BlocksProcessed6INT64

The number of AI blocks that the replication agent has applied to the target database.

Format >>>>>>>>>9

_ReplAgtAct-BlocksACK7INTEGER

The number of AI block acknowledgements that the replication agent sent to the replication server.

Format >>>>>>>>>9

_ReplAgtAct-NotesProcessed8INTEGER

The number of AI notes that the replication agent has applied to the target database.

Format ->>>>>>>>>9

_ReplAgtAct-LastTRID9INTEGER

Transaction ID (TRID) of the last transaction begin note that was applied to the target database by the replication agent.

Format ->>>>>>>>>9

_ReplAgtAct-Status10INTEGER

Current status of the replication agent.

A value from the Value column, as reported by the following command:
DSRUTIL -C status -detail

For more information, see DSRUTIL status qualifier .

Format >>>>>>>>9

_ReplAgtAct-CommStatus 11INTEGER The network communication status of the replication agent with the replication server.

Valid values are:

  • 1 — Connected
  • 2 — Disconnected

Format >>>>>>>>>9

_ReplAgtAct-State 12 CHARACTER Replication agent state. Valid values are:
  • Terminating
  • In Normal Processing
  • In Synchronization Processing
  • In Forced Transition
  • In Pre-Transition
  • Ready For Manual Transition

  • In Online Backup

  • Applying extent

  • Listening

  • Wait Resolve JTA

  • Connection Failed

  • In Startup Synchronization

  • In Recovery Synchronization

  • Being Transitioned

Format X(48)

_ReplAgtAct-Ready 13 INTEGER Replication agent ready status. Valid values are:
  • 0 — Not ready
  • 1 — Ready

Format >>>>>>>>9

_ReplAgtAct-WaitingFor 14 CHARACTER What the replication agent is waiting for. Valid values are:
  • Nothing
  • Schema Lock Request
  • Encryption Objects
  • Schema Object state change
  • Newest Encryption Keystore

Format X(48)

_ReplAgtAct-CurDelayInterval 15INTEGERCurrent message polling delay interval (in seconds).

Format >>>>>>>>9

_ReplAgtAct-TimeToTransition 16 CHARACTERThe time (in HH:MM:SS) remaining before automatic recovery transition.

Format X(24)

For more information, see Understand automatic transition with AI Streaming .

_ReplAgtAct-LastBlockReceived 17 CHARACTER The date and time when the replication agent last received an AI block from the replication server.

Format X(24)

_ReplAgtAct-TransStarted 18 INT64 The number of transaction begin notes that have been applied to the target database by the replication agent.

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-TransEnded 19 INT64 The number of transaction end notes that have been applied to the target database by the replication agent.

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-SyncPoints 20 INT64 The number of synchronization points1 that the replication agent has established with the replication server.

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-SrcRDBMSSeq 21 INT64 The sequence number of the AI extent containing the AI block being written to on the source database during forward processing of transactions at the time the replication server last assembled an AIBLOCK message for transmission to the replication agents.

-1 if not available

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-SrcRDBMSBlock 22 INT64 The block number of the AI block being written to the source database during forward processing of transactions at the time the replication server last assembled an AIBLOCK message for transmission to the replication agents.

-1 if not available

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-LastRecvBlockSeq 23 INT64 The sequence number of the AI extent containing the last AI block received by the replication agent.

-1 if not available

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-LastRecvBlockBlock 24 INT64 The block number of the last AI block received by the replication agent.

-1 if not available

Format ->>>>>>>>>>>>>>>>>>9

_ReplAgtAct-LastBlockSeq 25 INT64 The sequence number of the AI extent containing the most recent AI note that the replication agent began applying to the target database.

-1 if not available

Format ->>>>>>>>>>>>>>>>>>9
_ReplAgtAct-LastBlockBlock 26 INT64 The block number of the AI block containing the most recent AI note that the replication agent began applying to the target database.

-1 if not available

Format ->>>>>>>>>>>>>>>>>>9
_ReplAgtAct-ServerLag 27 INTEGER The time difference, measured in seconds, between the following events:
  • Time of note creation, during forward processing of transactions on the source database, of last transaction end, global transaction end, or AI extent switch note that was applied to the target database by the replication agent.
  • The last time an AI block was filled and sent to the PICA queue of the source database (factoring in the potential waiting time for a free plugin communication area (PICA) queue message entry) at the point when the replication server last assembled an AIBLOCK message for transmission to the replication agents.

-1 if not available

Format >>>>>>>>9

_ReplAgtAct-SourceTRID 28 INTEGERThe TRID of the last transaction started on the source database at the time the replication server last assembled an AIBLOCK message for transmission to the replication agents.

-1 if not available

Format >>>>>>>>9

_ReplAgtAct-LastSyncTimeTgt 29 CHARACTER The date and time when the replication agent last started applying a transaction begin, or AI extent switch note to the target database.

Format X(24)

_ReplAgtAct-LastSyncTimeSrc 30 CHARACTER The sum of _ReplAgtAct-LastSyncDelta and _ReplAgtAct-LastSyncTimeTgt. An approximate measure of the amount of lag that occurs when the last transaction end, global transaction end, or AI extent switch note is sent in an AI block from the replication server to the replication agent and when the replication agent actually starts to apply the note.

Format X(24)

_ReplAgtAct-LastSyncDelta 31 CHARACTER After successfully connecting to the replication agent, either during startup or recovery processing, the replication server sends five time-synchronization messages to that agent. On receiving each time-synchronization message, the replication agent computes the time difference between when the message was sent from the replication server and when it was received by the replication agent. This value represents the average of five different calculations. It provides an estimate of the network latency between the replication server and the replication agent.

Format X(24)

_ReplAgtAct-ServerBlocksToSend 32 INTEGER The count of AI Blocks in the PICA queue on the source database at the time the replication server last assembled an AIBLOCK message for transmission to the replication agents.

Format >>>>>>>>9
_ReplAgtAct-LastBlockCountTime 33 CHARACTER The date and time the replication agent last received an AIBLOCK message from the replication server. All AIBLOCK messages include a count of the number of AI Blocks in the plugin communication area (PICA) queue at the time of message assembly.

Format X(24)
_ReplAgtAct-BlockProcDelay 34 INTEGER The time difference, measured in seconds, between when the replication agent last received a timestamped AI block and when it began processing the AI notes in the block.

Format >>>>>>>>9
_ReplAgtAct-ReservedChar 35 CHARACTER Reserved for future use
_ReplAgtAct-ReservedInt 36 INTEGER Reserved for future use
1 Synchronization points are a collection of replication-related information (such as the last AI extent applied, the AI block number processed, the offset within an AI, and so on) that can be used as the starting point during synchronization in the event of the replication process being interrupted. After the synchronization points are applied to the target, the AI and BI are synced to the disc, and the server gets notified about these special points. During a restart, the server can use this information to start the synchronization process. If an AI block gets processed on the target but does not have synchronization point information in it, the block may or may not materialize on the disc. So, during a restart, the server has to start from the last synchronization point and retry the AI blocks after it. The server skips a block if it has been applied before; otherwise, the server applies the block. Therefore, you can see blocks being sent to target1 even if they are in sync with the source. The synchronization point information is available in both the .recovery file and the DSRUTIL monitor tool.