ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard
Configuration
- 1 Answers
- 5919 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-22339: cannot alter to not final since its attribute column is substitutable
ORA-01311: Illegal invocation of the mine_value function
ORA-33098: (APABBR01) A value of 'string' is not valid for the workspace object option.
ORA-01212: MAXLOGMEMBERS may not exceed string
DRG-10703: invalid framework object string
ORA-21710: argument is expecting a valid memory address of an object
ORA-31193: This versioning feature isn't supported for resource string
NNL-01043: Data stream answer failures: number
ORA-29823: object being analyzed is not a table
ORA-38901: column "string" of table "string" must be one of the first "number" columns
TNS-04004: Unable to encrypt the supplied password.
ORA-39004: invalid state
Oracle Errors 
