Oracle Restart Attempts To Mount An Already Started Database After Switchover From Standby
(Doc ID 1663182.1)
Last updated on FEBRUARY 19, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.4 [Release 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
1. A successful Data Guard broker-managed switchover is accomplished.
2. The former primary database, which is now the physical standby, is successfully shut down and restarted to a mount, per the alert.log.
3. AFTER this database has already been mounted, Oracle Restart attempts to issue another startup mount command. At exactly the same time, an ora-600 [ksfglt:no_proc] is produced.
Changes
After a Data Guard broker-managed switchover the former primary database, which is now the physical standby, is successfully shut down and restarted to a mount. Oracle Restart however fires another startup mount of the already mounted database instance.
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 |