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-16727: resource guard cannot close database
ORA-38403: attribute set name may not be longer than 22 characters
LPX-00304: input parameter to function is null
ORA-17612: Failed to discover Oracle Disk Manager library, return value string
KUP-11002: unable to read data chunk string
ORA-31103: Resource locked in shared mode. Cannot add exclusive lock
ORA-31608: specified object of type string not found
SQL*Loader-00962: Error setting user-side Ctrl-C handler
ORA-32576: missing TYPE keyword
DRG-11504: invalid longsize parameter of string specified
KUP-03007: end position (number) is less than start position (number) for range
ORA-08320: scnget: Call to scnget before scnset or scnfnd.