ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard
Configuration
- 1 Answers
- 6089 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-19800: Unable to initialize Oracle Managed Destination
ORA-08182: operation not supported while in Flashback mode
NNL-01005: UNKNOWN TYPE responses received: number
DRG-10206: failed to perform recovery for a server or client
PCB-00009: Cannot change MAXLITERAL after an EXEC SQL statement
ORA-14401: inserted partition key is outside specified partition
NZE-28856: Buffer overflow error
ORA-36991: (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.
ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
NNO-00312: listen address string is invalid
ORA-39076: cannot delete job string for user string
ORA-14457: disallowed Nested Table column in a Temporary table
Oracle Errors 
