RMAN Catalog Returning Error RMAN-06004: ORA-20999 (Doc ID 1969061.1)

Last updated on APRIL 19, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Goal


Initial Configure DB_UNIQUE_NAME is successful, which is more than 30 chars in length
"if no config entries exist already".

Later on, all catalog operations fail with ORA-20999

 

Configured db_unique_name using large string:

RMAN-06601: new RMAN configuration parameters:
RMAN-01005: CONFIGURE DB_UNIQUE_NAME 'ABCDEF01_USVALIDA01.MYORACLESUP.com' CONNECT IDENTIFIER 'ABCDEF01_USVALIDA01.MYORACLESUP.com_NNNNNQ01_SBY';
RMAN-06604: new RMAN configuration parameters are successfully stored
RMAN-08225: configuration changes, starting full resync of recovery catalog
RMAN-08004: full resync complete

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 06/04/2014 13:14:41
RMAN-06614: DB_UNIQUE_NAME string is too long

RMAN> show all;

RMAN configuration parameters for database with db_unique_name NWCARQ04_USVALDB020 are:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 06/04/2014 13:19:18
RMAN-06004: ORACLE error from recovery catalog database: ORA-20999: internal error: found non-null and null site name


 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms