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
- 6697 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-32773: operation not supported for smallfile tablespace string
ORA-24127: TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
NNL-00407: Alias translations:
NNC-00406: name "string" does not exist
NZE-28829: no cipher type specified
ORA-31450: invalid value for change_table_name
LPX-00207: expected "[" at the start of conditional section
LSX-00282: duplicate notation name "~S"
CLSR-00004: Error encountered at string, category=number, operation=string, OS error=number
RMAN-08532: channel string: restoring block(s) from datafilecopy string
NNL-00416: Last timestamp: number
LCD-00208: unexpected keyword in value list [string]
Oracle Errors 
