ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration

Cause : Thes pecfiiedD B_UINQUEN_AMEi s nto int he aDta uGardC onfgiuraiton.

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

If hte D_GCONIFG attribtue o ftheL OG_RACHIEV_COFNIG apramteer si enbaled ,youm usts pecfiy av ali dDB_NUIQU_ENAM.E Th elis tof avlidD B_UINQUEN_AME scanb e seen wtih teh V$ADTAGAURD_OCNFI Gvie.w Thsi prbolemc an laso cocurw hens pecfiyin ga nno-stnadbyd estniatino wiht anD B_UINQUEN_AMEa ttrbiutet hatd oesn ot amtcht he BD_UNQIUE_ANME niitilaizaiton apramteer ofr teh currenti nstnace.

update : 22-08-2017
ORA-16053

ORA-16053 - DB_UNIQUE_NAME string is not in the Data Guard Configuration
ORA-16053 - DB_UNIQUE_NAME string is not in the Data Guard Configuration

  • ora-36163 : (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time.
  • ora-28558 : HS_FDS_CONNECT_STRING undefined for non-Oracle system
  • ora-26712 : remote object is "string"."string"@"string"
  • ora-06524 : Unsupported option : string
  • ora-01268 : invalid TEMPFILE clause for alter of permanent TABLESPACE
  • ora-01920 : user name 'string' conflicts with another user or role name
  • ora-38461 : XML Tag "string" already exists for the XMLType attribute "string"
  • ora-23424 : materialized view "string"."string" at string not registered
  • ora-25278 : grantee name cannot be NULL
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-13039 : failed to update spatial index for element string.string.string
  • ora-04033 : Insufficient memory to grow pool
  • ora-28234 : key length too short
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-31231 : DBMS_LDAP: invalid PROPERTY_SET
  • ora-02483 : Syntax error in process specification (string)
  • ora-12436 : no policy options specified
  • ora-15120 : ASM file name 'string' does not begin with the ASM prefix character
  • ora-29300 : ORACLE error, tablespace point-in-time recovery
  • ora-22973 : size of object identifier exceeds maximum size allowed
  • ora-37150 : line string, column string, string
  • ora-30054 : invalid upper limit snapshot expression
  • ora-07704 : error in archive text: need ':' after device name
  • ora-29540 : class string does not exist
  • ora-06933 : CMX: error during attach
  • ora-26765 : invalid parameter "string" for downstream capture "string"
  • ora-32814 : propagation schedule string does not exist
  • ora-09763 : osnmpx: send/receive error exchanging Mach ports.
  • ora-40283 : missing cost matrix
  • ora-39096 : invalid input value string for parameter string
  • 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.