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 |
QSM-02117: missing GROUPING_ID or GROUPING functions on GROUP BY column(s)
ORA-01688: unable to extend table string.string partition string by string in tablespace string
ORA-22328: object "string"."string" has errors. string
TNS-12602: TNS: Connection Pooling limit reached
ORA-31204: DBMS_LDAP: PL/SQL - Invalid LDAP Session.
ORA-24338: statement handle not executed
QSM-01026: query rewrite is disabled for, string
ORA-12711: this CREATE CONTROLFILE character set is not allowed
ORA-24505: cannot change character set id on the handle
TNS-02526: server proxy type does not match client type
ORA-13626: The specified object string is not valid for task string.
ORA-24776: cannot start a new transaction