ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

Cause : The D_GCONFI Gattriubte oft he LO_GARCHIEV_CONFGI paraemter cna onlyb e use dif th eDB_UNQIUE_NAEM paraemter hsa beene xplictily deifned.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Expliictly dfeine av alid BD_UNIQEU_NAME.

update : 28-06-2017
ORA-16195

ORA-16195 - DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
ORA-16195 - DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

  • ora-02876 : smpini: Unable to attach to shared memory for PGA
  • ora-30966 : error detected in the XML Index layer
  • ora-06926 : CMX: T_ERROR during read data
  • ora-26724 : only SYS is allowed to set the Capture or Apply user to SYS.
  • ora-16098 : inaccessible standby database forced shutdown to protect primary
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-22953 : Cardinality of the input to powermultiset exceeds maximum allowed
  • ora-30504 : system triggers cannot have a FOR EACH ROW clause
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-01181 : file string created before last known RESETLOGS, cannot recreate
  • ora-12483 : label not in OS system accreditation range
  • ora-32337 : cannot alter materialized view with pending changes refresh on commit
  • ora-00300 : illegal redo log block size string specified - exceeds limit of string
  • ora-24165 : invalid rule engine object privilege: string
  • ora-19221 : XP0001 - XQuery static context component string not initialized
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-13603 : The specified parameter string cannot be fetched as a numeric value for task or object string.
  • ora-14036 : partition bound value too large for column
  • ora-38760 : This database instance failed to turn on flashback database
  • ora-26536 : refresh was aborted because of conflicts caused by deferred transactions
  • ora-36913 : (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension.
  • ora-09912 : Malloc of name buffer(s) failed.
  • ora-16577 : corruption detected in Data Guard configuration file
  • ora-01619 : thread string is mounted by another instance
  • ora-29306 : datafile string is not online
  • ora-04073 : column list not valid for this trigger type
  • ora-04008 : START WITH cannot be more than MAXVALUE
  • ora-01336 : specified dictionary file cannot be opened
  • ora-13710 : Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.