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
- 6812 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 |
NNL-00350: No save config currently scheduled
NID-00126: Database should have no datafiles in unknown state
NPL-00101: uninitialized ASN.1 context
CLSR-00502: Error number encountered when subscribing an EVM event
ORA-09811: Unable to initialize package.
ORA-13765: Value "string" is illegal for a result limit.
ORA-22604: TDS handle already generated
ORA-38454: attribute set not defined for the column being indexed
ORA-25254: time-out in LISTEN while waiting for a message
ORA-02345: cannot create a view with column based on CURSOR operator
ORA-09824: Unable to enable allowmacaccess privilege.
DRG-12602: index owner does not have access to user datastore procedure: string
Oracle Errors 
