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
- 6815 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-16774: Error in stopping the physical apply service (MRP process)
ORA-01233: file string is read only - cannot recover using backup controlfile
ORA-27011: skgfrd: cannot read from file opened for write
DRG-11624: invalid attribute string for string: proper range string to string
ORA-13024: polygon has less than three segments
DRG-13303: value of wildcard offset must be in the range string..string, at line string
TNS-12585: TNS:data truncation
ORA-13419: cannot perform mosaick operation on the specified table column
ORA-24035: AQ agent string is not a subscriber for queue string
NNL-00209: Cache checkpoint interval is currently string
ORA-36280: (XSCGMDLAGG08) The dimension of valueset workspace object is not in the dimension list of the current compiling model.
PLS-00309: with %%LAST attribute, 'string' must be a variable of an enumerated type
Oracle Errors 
