Once Dbvisit Replicate is configured and starts replicating data the replication should be monitor regularly. Major aspects of replication to be monitored are:
- Status of MINE and APPLY
- Check for conflicts
- Lag between source and target
- Long running transactions (upon MINE/APPLY process restarts Dbvisit Replicate will go back to the beginning of any uncommitted transactions and the associated PLOG for this, so these should be monitored and cleaned up by the DBA/Administrator)
Dbvisit Replicate provides notification and remote management feature which can be tuned to send email alerts about replication status and issues. Most of the information required for monitoring is not stored in the database, but available using the dbvrep console. Following are some generally used basic monitoring commands. Click here for complete command line reference.
- LIST STATUS
- LIST CONFLICT
- LIST STATS
The commands can be specified directly on the command line and you can even use --silent to suppress the usual header.
$bash start-console.sh --silent LIST STATUS
Example (to check for any long running transactions):
$bash start-console.sh --silent LIST TRANSACTIONS
Some customers prefer to build their own monitoring scripts. See Heartbeat table for more information.