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-22061: invalid format text [string]
ORA-31672: Worker process string died unexpectedly.
ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.
ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page
PCC-00106: RELEASE is an Oracle extension to the COMMIT and ROLLBACK statements
ORA-31652: command response message was invalid type - detaching job
RMAN-06508: MAXSETSIZE string kbytes should be greater than blocksize string bytes
ORA-26510: materialized view name: 'string' is greater than max. allowed length of string bytes
NNL-00278: Maximum number of times a request can be reforwarded is now number
PCC-00142: No EXEC SQL CONTEXT USE statement encountered
DGM-16949: "string" was not found
ORA-22854: invalid option for LOB storage index