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
- 6724 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-14510: can specify VALIDATE INTO clause only for partitioned tables
ORA-02721: osnseminit: cannot create semaphore set
LSX-00234: invalid decimal "~S"
ORA-28038: disallow O2LOGON
LPX-00207: expected "[" at the start of conditional section
ORA-13156: table to be registered string.string is not empty
TNS-00132: COST value must be an integer greater than 0
ORA-29377: consumer group string is not part of top-plan string
RMAN-06212: Object Type Filename/Handle
RMAN-10034: unhandled exception during execution of job step number, error unknown
ORA-19609: %s is from different backup set: stamp string count string
LSX-00230: invalid integer "~S"
Oracle Errors 
