This section describes possible replication problems and solutions.
Monitoring Oracle replication lagTo monitor replication lag in Amazon CloudWatch, view the Amazon RDS ReplicaLag metric. For more information about replication lag time, see Monitoring read replication and Amazon CloudWatch metrics for Amazon RDS.
For a read replica, if the lag time is too long, query the following views:
V$ARCHIVED_LOG â Shows which commits have been applied to the read replica.
V$DATAGUARD_STATS â Shows a detailed breakdown of the components that make up the ReplicaLag metric.
V$DATAGUARD_STATUS â Shows the log output from Oracle's internal replication processes.
For a mounted replica, if the lag time is too long, you can't query the V$ views. Instead, do the following:
Check the ReplicaLag metric in CloudWatch.
Check the alert log file for the replica in the console. Look for errors in the recovery messages. The messages include the log sequence number, which you can compare to the primary sequence number. For more information, see Amazon RDS for Oracle database log files.
If you add or modify any triggers, and if replication fails afterward, the problem may be the triggers. Ensure that the trigger excludes the following user accounts, which are required by RDS for replication:
User accounts with administrator privileges
SYS
SYSTEM
RDS_DATAGUARD
rdsdb
For more information, see Miscellaneous considerations for RDS for Oracle replicas.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4