ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard
Configuration
- 1 Answers
- 5735 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 |
ORA-25401: can not continue fetches
ORA-27507: IPC error disconnecting from a port
ORA-13775: inconsistent datatype in input cursor
ORA-13636: The specified value string provided for parameter string is not valid for this advisor.
TNS-01409: Instance "string"
QSM-02175: some query block in UNION ALL MV is not fast refreshable
ORA-13836: invalid attribute value specified
ORA-19642: incremental-start SCN is string
ORA-23469: %s is different between templates
PLS-00147: LIBRARY file specification string is empty
PCC-02066: CMD-LINE: Could not find or could not open system config file
TNS-00301: ***Enabling Interchange : string
Oracle Errors 
