Table 5–12: Replication Agent Status details
Field
|
Description
|
|
Indicates whether the database is enabled as a replication source or target.
|
|
Lists basic remote agent information.
|
|
Lists the name of the remote agent.
|
|
Lists the remote agent identification number.
|
|
Lists the host on which the target database associated with the remote agent resides.
|
|
Shows agent processing information:
- Normal processing — The server and agent are performing normal processing.
- Initial connection — The agent is waiting for initial connection from server.
- Startup synchronization — The server and agent are synchronizing.
- Initialization — The agent is being initialized by the server.
- Initial connection failed — The server could never connect an agent.
- Invalid target database configuration — Something in the target database does not match the source.
- Agent terminated — The target database shut down or agent terminated using
Terminate agent .
- Online backup of Target Database — An online target database backup is being performed.
- Recovery synchronization — Recovery synchronization is being performed.
- Recovery failed — Failure recovery was unsuccessful.
- Unknown — The agent is in an unknown state.
|
|
Lists whether the remote agent is a critical agent (Yes) or not (No).
|
|
Lists the replication method: asynchronous or synchronous.
|
|
Shows why the agent might be waiting. The field value might be one of the following:
- Nothing — Indicates no waiting is taking place
- Schema lock request — Indicates the server is waiting for the agent to acquire the schema lock so the database schema can be changed
|
|
Shows the maximum number of bytes used for the TCP/IP communication messages.
|
|
Shows the date and time at which the server and agent connected.
|
|
Shows the amount of time, in milliseconds, the agent will wait between polling the TCP/IP connection for information to be replicated. Current is the current value, min is the minimum value, and max is the maximum value.
Polling is used to increase the performance of the server, and the wait is used to limit the amount of overhead when no data is available to be replicated.
|
|
Shows a group of remote agent-related transition information.
|
|
Shows the type of transition to be performed:
- Manual — Indicates intervention is required to complete the transition of a target database to a normal OpenEdge database
- Automatic — Indicates a transition from a target database to a normal OpenEdge database will take place without intervention
|
|
Shows the date and time the last block was sent to the agent.
|
|
Shows a selection of activity information.
|
|
Shows the number of blocks received from the server.
|
|
Shows the number of blocks processed.
|
|
Shows the number of blocks acknowledged.
|
|
Shows the number of AI transaction notes processed by the agent.
|
|
Shows the number of transactions started on the agent.
|
|
Shows the number of transactions completed on the agent.
|
|
Shows the number of synchronization points that have occurred.
|
|
Identifies the current AI block that is being written by the source database and provides the last AI block that was sent by Replication.
|
|
Provides the current source database block that the OpenEdge Replication agent is processing.
|
|
Provides the last source database block that the OpenEdge Replication agent processed.
|
|
Provides latency information that shows how far behind OpenEdge Replication is in updating the target database. This is important if the target database is transitioned due to source database failure.
|
|
Provides the number of seconds the OpenEdge Replication server is behind the source database.
|
|
Provides the current source database transaction that the OpenEdge Replication agent is processing.
|
|
Provides the last source database transaction that was applied to the target database.
|
|
Provides the date of the last transaction applied to the target database by the OpenEdge Replication agent based on source database time.
|