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
- 6667 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 |
RMAN-06738: database name "string" is not unique in the recovery catalog
DRG-52203: invalid object name: string
ORA-38101: Invalid column in the INSERT VALUES Clause: string
RMAN-06500: skipping backupset key string; already backed up string time(s)
LPX-00204: syntax error
TNS-02520: encryption/crypto-checksumming: no Diffie-Hellman seed
ORA-39001: invalid argument value
PLS-00604: aggregate function is not allowed here
DRG-10303: could not queue given commands to be processed
PCB-00238: Element of this table group item host variable cannot be a table
ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.
ORA-24088: AQ Agent string does not exist
Oracle Errors 
