ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard
Configuration
- 1 Answers
- 5749 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-24811: less data provided for writing than indicated
ORA-01508: cannot create database; error in file 'string' at line string
DRG-12800: Attribute NESTED_TYPE must have owner name as prefix
NZE-29030: SSL handshake is requested.
QSM-01106: MV, string, is stale with respect to some partition(s) in the base table(s)
ORA-16510: messaging error using ksrwait
ORA-30088: datetime/interval precision is out of range
ORA-01074: cannot shut down ORACLE; inside a login session - log off first
NPL-00102: missing stream functions in ASN.1 context initialization
ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
ORA-30118: syntax error at 'string' at the end of input
ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
Oracle Errors 
