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 |
ORA-30514: system trigger cannot modify tablespace being made read only
QSM-00753: the specified value string is out of the acceptable range of string to string for parameter string
RMAN-06127: skipping read-only file string
ORA-26667: invalid STREAMS parameter string
TNS-00549: value specified for the SSL version is not valid
ORA-10561: block type 'string', data object# string
RMAN-06116: cannot crosscheck unavailable object
ORA-07247: skgfrfms, skgfrnms: read error, unable to read block from database file
SQL*Loader-00305: More than one end of file character encountered
NZE-29048: Unexpected message received.
ORA-23409: could not find an unused refresh group number
ORA-00110: invalid value string for attribute string, must be between string and string