My Oracle Support Banner

Automatic Restart of Databases during Switchover fail with ORA-12514 in DGMGRL (Doc ID 308943.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
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

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 Database:
DB_NAME: DG1

 

 

Performing a switchover operation in a DataGuard environment requires a shutdown of both the (former) primary database and the (former) standby database. 

During Switchover using DGMGRL the Databases need to be restarted (these symptoms could happen with any operation in DGMGRL that requires an automatic database restart).

The automatic restart of the databases fails with

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

The error in DGMGRL may look like this:

Operation requires startup of instance "DG1" on database "Primary".
Starting instance "DG1"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "DG1".
You must start instance "DG1" manually.

Changes

One of the documented prerequisites for first use from the DataGuard Broker manual requires that a special entry be set up in each relevant listener.ora file to enable DGMGRL to automatically startup databases included in this configuration.  Failure to execute this prerequisite will result in the above mentioned symptoms upon switchover. 

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.