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
- 6549 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-01482: unsupported character set
ORA-19000: missing RELATIONAL keyword
PCC-00056: FOR clause not allowed on SELECT statement at line number in file string.
NZE-29190: Multiple entries in OID
RMAN-08019: channel string: restoring datafile string
NNL-00814: Total query processing time: string
ORA-01985: cannot create user as LICENSE_MAX_USERS parameter exceeded
ORA-15015: invalid _ASM_LIBRARIES initialization parameter 'string'
QSM-01601: rollup(s) took place on equivalence, string
ORA-16643: unable to determine location of broker configuration files
ORA-22608: cannot add an attribute to the already generated image handle
ORA-09946: File name too long for buffer
Oracle Errors 
