Kbase P115066: What clues indicate that my replication source database has stopped communicating with my replicatio
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/2/2007 |
|
Status: Verified
GOAL:
What clues indicate that my replication source database has stopped communicating with my replication target database.
GOAL:
What tools can help me identify if my replication source database has stopped communicating with my replication target database?
GOAL:
Best practices for determining if replication has stopped between the source and target database.
GOAL:
target database stops, is there some way of raising an email type alert to somebody
FIX:
The Fathom\OpenEdge product is designed for exactly this type of detection. In the OpenEdge 3.1B01 product, these are supplied in the default 'replication rules' section. In earlier versions, as for any monitoring, the rules can be setup manually.
Otherwise:
The following command run against the primary |source database will determine how many "LOCKED" status after imaging files there are:
$ rfutil source -C aimage list
If there are several ai files in a LOCKED status, then Replication is likely not taking place.
This can be confirmed by running the following command against either the target database:
$ dsrutil dbname -C monitor
The following error is returned when the Repilcation Agent (RPLA) has stopped:
Cannot attach to replication shared memory, status=-1
Otherwise the utility will return the replication status among other metrics, example:
State Normal Processing
Another method is monitoring the target.lg file for the message:
The Fathom Replication Agent is shutting down. (10482)