I am using OE Replication Plus, which allows read-only activity on my target database. What do I monitor and how? What do I watch for?
The replication target server's primary role is to ensure that your replication target database resembles your source database to the greatest extent possible. You want to ensure that no other activity interferes with this primary objective.
Indicators from ProTop that the target is or might be in danger of getting behind the source are:
- alerts for picaFree, picaUsed, picaUsedPct, agentStatus, agentCommStat
- alerts for locked after-image files (Locked AI Extents) are a clear indicator that the source and targets are already out of sync
How? Install ProTop!
Use your existing customer ID and select the option to discover running databases and provide the directory the target db is running in.
Be sure to add dbmonitor.sh to cron on your Linux system as you have on your source database server.
Copy etc/alert.cfg to etc/alert.[custid].cfg and follow the suggestions in the next section.
Alert Adjustments
If you are not running After Imaging on the target database, comment out the alert definitions that begin "ai_" in your alert.*.cfg file, as well as con_AIW, con_BIW, con_APW, con_AIMD.
Comment out the alert definition for old transactions (otrx). Those are reported by ProTop running on the source database and would only serve to duplicate those alerts.
Comment out any other alert definitions for alerts you receive and do not find useful for the target database.
SQL
If using SQL, update SQL stats on the source database regularly and follow SQL Best Practices.
Server Considerations
Record your target db server metrics using Telegraf. The trends can help pinpoint when something changed.
If your reporting users connect to the database using -S and -H, be sure to use the Prefetch database parameters.
Can reports be run during nonpeak business hours?