My Oracle Support Banner

RAC Instance Can't Be Started After db_unique_name Change: PRCR-1013, PRCR-1064, CRS-2674 (Doc ID 1943172.1)

Last updated on JANUARY 07, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.

Symptoms

After modify the db_unique_name for a standby database PROD to PROD_EAST, then remove and add the database back to OCR, it can not be started any more on node 1 either via srvctl or sqlplus, but the instance starts fine on node 2.

 It appears a shutdown abort is issued as soon as the instance is started.

Changes

Changed db_unique_name for this database and remove/add it back to OCR.

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.