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 |
SQL*Loader-00523: error number writing to file (string)
TNS-00270: %s: Terminal Error string
ORA-31003: Parent string already contains child entry string
ORA-01043: user side memory corruption [string], [string], [string], [string]
SQL-02154: Invalid or unset data type for host variable in ANSI Dynamic
ORA-12446: Insufficient authorization for administration of policy string
ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-13047: unable to determine ordinate count from table <layer>_SDOLAYER
ORA-15013: diskgroup "string" is already mounted
EXP-00090: cannot pin type "string"."string"
ORA-14101: partition extended table name cannot refer to a synonym
SQL*Loader-00911: Error defining output variable(s) for upi: [number]