Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard
Configuration
- 1 Answers
- 6718 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The specified DB_UNIQUE_NAME is not in the Data Guard
Configuration.
Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG
parameter is enabled, you must specify a valid
DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be
seen with the V$DATAGUARD_CONFIG view. This problem can also
occur when specifying a non-standby destination with an
DB_UNIQUE_NAME attribute that does not match the
DB_UNIQUE_NAME initialization parameter for the current
instance.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 0 No |
KUP-04066: error initializing access to external table source
ORA-02082: a loopback database link must have a connection qualifier
ORA-18002: the specified outline does not exist
ORA-01969: You must specify RESETLOGS or NORESETLOGS
TNS-12625: TNS:missing argument
QSM-01126: query rewritten with set operator materialized view, string
ORA-28292: No Domain Policy registered for Kerberos based authentication
O2F-00326: Some characters in this name were not legal identifier characters
ORA-08449: invalid numeric symbol found in picture mask
ORA-31698: Error stack buffer size must be specified and must be greater than 0.
ORA-32696: HTI: No free slot
ORA-22953: Cardinality of the input to powermultiset exceeds maximum allowed
Oracle Errors 
