After Switchover using Dataguard Broker there is a Gap between primary and standby And The Archive Logs Are Not On Tape Or Disk
(Doc ID 2158808.1)
Last updated on JANUARY 06, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Switchover test from our primary database to our standby database and then another switchover back to our primary. After the last switchover , standby has a gap and the required archivelogs are not available on tape or disk.
The following error snippet might be experienced:
THREAD# TIMESTAMP MESSAGE
1 06-JUL-2016 14:11:18 PING[ARC0]: Heartbeat failed to connect to standby '<name>'. Error is 16146.
1 06-JUL-2016 14:11:21 PING[ARC0]: Heartbeat failed to connect to standby '<name>'. Error is 16146.
1 06-JUL-2016 14:11:22 LGWR: Error 16146 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host '<name>'
1 06-JUL-2016 14:11:22 Error 16146 for archive log file 3 to '<name>'
1 06-JUL-2016 15:07:13 Error 3113 for archive log file 7 to '<name>'
1 06-JUL-2016 15:07:15 LGWR: Error 1041 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host '<name>'
1 06-JUL-2016 15:07:28 Error 1034 received logging on to the standby
1 06-JUL-2016 15:07:28 ARC0: Error 1034 attaching to RFS for reconnect
1 06-JUL-2016 15:07:28 PING[ARC0]: Error 3113 when pinging standby <name>.
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 |
| Cause |
| Solution |
| References |