ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly
defined
Answer / guest
Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG
parameter can only be used if the DB_UNIQUE_NAME parameter
has been explicitly defined.
Action: Explicitly define a valid DB_UNIQUE_NAME.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
PCC-02320: arithmetic expression does not have correct operand types
DRG-50804: failed to exec cursor
NZE-28813: invalid record type
NZE-28815: Cannot convert a number in native format to Oracle format.
NZE-29024: Certificate validation failure
ORA-31194: Resource string is already deleted
NNL-00278: Maximum number of times a request can be reforwarded is now number
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-24305: bad bind or define context
QSM-01005: no query rewrite when query has slave SQL
ORA-30161: A system error occurred during the OCIFile function call
QSM-01069: summary join graph for, string, does not have table, string