Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly
defined
- 1 Answers
- 3306 Views
- I also Faced
- E-Mail Answers
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 |
SQL*Loader-00943: incorrect datafile string specified for table string partition string
ORA-25240: message ID and dequeue condition/correlation ID specified in dequeue options
ORA-24434: OCIStmtRelease called before OCIStmtPrepare2.
ORA-26079: file "string" is not part of table string.string
PLS-00251: RETURN, for actual function return, must be last in the parameters clause
ORA-23487: object groups "string"."string" and "string"."string" do not have the same connection qualifier
LFI-00118: Unable to change type to Unknown.
ORA-29309: export dump file was generated by different version of DBMS_PITR package
ORA-24419: Proxy sessions are not supported in this mode.
ORA-09365: Windows 3.1 Two-Task driver unable to destroy hidden window
ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT and NTEXT.
ORA-16205: DDL skipped due to skip setting
Oracle Errors 
