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 : 23-04-2017

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

  • ora-02038 : define is not allowed for array type
  • ora-23333 : column string is already part of a column group
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-16785 : the database is not in ARCHIVELOG mode
  • ora-01909 : REUSE keyword expected
  • ora-25111 : creation of BITMAP cluster indices is not supported
  • ora-06402 : NETCMN: error receiving break message
  • ora-39142 : incompatible version number string in dump file "string"
  • ora-23465 : flavor already includes column string of "string"."string"
  • ora-29820 : the statistics type is not present
  • ora-28542 : Error in reading HS init file
  • ora-24433 : This statement has already been prepared using OCIStmtPrepare2.
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-25270 : sender info does not match with the actual sender of the message
  • ora-32125 : Attribute type is not appropriate
  • ora-16755 : failed to set initialization parameter
  • ora-03126 : network driver does not support non-blocking operations
  • ora-00260 : cannot find online log sequence string for thread string
  • ora-12504 : TNS:listener was not given the SID in CONNECT_DATA
  • ora-01314 : Name of the column to be mined should be a string literal
  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-28177 : incorrect Kerberos ticket version
  • ora-39206 : A parallel degree of string is invalid.
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-26684 : invalid value for value_type
  • ora-06755 : TLI Driver: cannot close transport endpoint
  • ora-13601 : The specified Advisor string does not exist.
  • ora-24122 : invalid block range specification
  • ora-12201 : TNS:encountered too small a connection buffer
  • 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.