ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard
Configuration
- 1 Answers
- 5708 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 |
LPX-00234: namespace prefix "~S" is not declared
ORA-02031: no ROWID for fixed tables or for external-organized tables
ORA-16014: log string sequence# string not archived, no available destinations
ORA-32129: cannot get information about this column
DRG-12013: This method has already been performed - repeat operation?
QSM-02050: subquery using the ALL clause in mv
ORA-13914: Threshold notification failed.
ORA-31093: null or invalid value specified for parameter : string
ORA-13158: Oracle object string does not exist
ORA-23421: job number string is not a job in the job queue
ORA-02831: Segment deallocation failed - empty segment list
RMAN-06062: can not backup SPFILE because the instance was not started with SPFILE
Oracle Errors 
