My Oracle Support Banner

REINSTATE of OLD CRS configured PRIMARY database fails with ORA-16653 (Doc ID 2127510.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.0 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 Backup 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:

Database name: PRIM

TNS_ADMIN for GI HOME: TNS_ADMIN=/usr/ora11g/grid/11.2.0.4/network/admin

TNS_ADMIN for RDBMS HOME: TNS_ADMIN=/usr/ora11g/app/oracle/product/11.2.0.4/db/network/admin

ORA_CRS_HOME=/usr/ora11g/grid/11.2.0.4

ORACLE_BASE=/usr/ora11g/oragrid

ORACLE_HOME = /usr/ora11g/app/oracle/product/11.2.0.4/db

 

 

 

 

Changes

 This environment has different TNS_ADMIN for GI and RDBMS HOME's. The owner of both ORACLE_HOME's is the same user ora11g.

TNS_ADMIN for GI HOME: TNS_ADMIN=/usr/ora11g/grid/11.2.0.4/network/admin

TNS_ADMIN for RDBMS HOME: TNS_ADMIN=/usr/ora11g/app/oracle/product/11.2.0.4/db/network/admin

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


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