Tags

11g (5) 12c (6) 18c (3) 19c (4) ASM (1) Critical Patch (11) Data Pump (1) Dataguard (9) Diverse (3) GRID (7) GitLab (2) Linux (8) OEM (2) ORA Errors (13) Oracle (12) RMAN (4)

Saturday, March 28, 2020

ORA-16053: DB_UNIQUE_NAME is not in the Data Guard Configuration



ORA-16053: DB_UNIQUE_NAME is not in the Data Guard Configuration

PURPOSE: All documents are provided on this Blog just for educational purposes only.  Please make sure that you run it in your test environment before to move on to production environment. 

SQL> alter system set LOG_ARCHIVE_DEST_1='LOCATION=+DATA VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=EDUDB01';
alter system set LOG_ARCHIVE_DEST_1='LOCATION=+DATA VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=EDUDB01'
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16053: DB_UNIQUE_NAME EDUDB01 is not in the Data Guard Configuration

SOLUTION:

srvctl remove database -d edudb
srvctl add database -d EDUDB01 -oraclehome /oracle19c/product/19.6.0.0/db
srvctl modify database -d EDUDB01 -oraclehome /oracle19c/product/19.6.0.0/db -p +DATA/EDUDB/PARAMETERFILE/spfile.270.1034096743
srvctl config database -d EDUDB01

alter system set db_unique_name=xxx scope=spfile;

Done:

No comments:

Post a Comment

physical standby without duplicate command

physical standby without duplicate command create a physical standby database using RMAN without using duplicate command PURPOSE:   All docu...