Logs are not shipped to the physical standby database
(Doc ID 1130523.1)
Last updated on AUGUST 21, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Affected Database: Generic (All Databases)
Symptoms
*** Reviewed for Relevance 15-Jul-2015 ***
May encounter different types of errors depending on the situations:
- Logs are not shipped at log switch or fal archiving fails
- Value of applied column on the primary is not consistent as that on the standby
- RMAN does not delete logs and results in error RMAN-08137
- In some rare cases ORA-12154 may show up in the primary alert log
- Other possible errors ORA-3113, ORA-3135
- WARN: ARCH: Terminating pid <PID> hung on an I/O operation
krsv_proc_kill: Killing 1 processes (Process by index)
Changes
Problem usually occurs after OS or network errors, or restarting the primary or standby instance or reboot the primary or standby node that abruptly crashes log shipping between the primary and standby
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |