Log shipping in Oracle database involves continuously sending redo logs from the primary database to standby databases, ensuring data consistency and availability for disaster recovery and high availability scenarios.
The last DR sync date alert is triggered from the standby database when there is a failure in the Oracle database log shipping mechanism.
Symptoms
When a switchover or failover operation is made and encounters errors or takes longer than expected, it could indicate issues with the standby database not being up-to-date or in sync with the primary.
Impact: Critical
A log shipping failure can lead to data loss due to inconsistencies between primary and standby databases, potentially resulting in extended downtime during recovery scenarios.
Expected behavior
Log shipping must be reliable and effective for disaster recovery and high availability.
Recommendations
Proactively monitor log shipping failures and troubleshoot when issues are detected. Investigate the root cause by reviewing logs, checking network connectivity, ensuring sufficient disk space, and verifying configuration parameters.
AimBetter simplifies this troubleshooting once you receive alerts related to the components involved and the logs are available in a friendly interface.
