Database Administration (MOSC)

MOSC Banner

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

edited Nov 8, 2019 6:58AM in Database Administration (MOSC) 5 commentsAnswered ✓

Hello.

I am seeing this error in 11.20.4 database

  1  select dest_id, destination, status, error, fail_date from v$archive_dest

  2*

oradba@pdcint10>/

   DEST_ID DESTINATION                    STATUS    ERROR                          FAIL_DATE

---------- ------------------------------ --------- ------------------------------ -------------------

         1 +RECO_NAEP11/pdcint20/archivel VALID

         2 pdcint10                       BAD PARAM ORA-16053: DB_UNIQUE_NAME  is  03-04-2016 12:31:06

                                                    not in the Data Guard Configur

                                                    ation

Not sure what is causing it

Here are my unique names

Primary - oradba@pdcint10>show parameter uniq

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

db_unique_name                       string      pdcint20

Snadby -pdcint10>show parameter uniq

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

db_unique_name                       string      pdcint10

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center