Data guard Switchover Via Broker Fails With ORA-12523/ORA-12518
(Doc ID 2150384.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Primary Databases: PRIMARY201, PRIMARY202
Standby Databases: STANDBY201,STANDBY202
Instance Names: DB1
2 node RAC
Oracle Data guard replication using physical standby DB
Primary DBs: primary201 and primary202
Standby DBs: standby201 and standby202
Real-time apply, no ssh tunneling used.
Static Listeners are used for DB connections.
Switch over via Broker was called on standby201 and failed due to any one of the reason,
UR=A is used for connection to a database which is not mounted.
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