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 : 25-06-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-27302 : failure occurred at: string
  • ora-25128 : No insert/update/delete on table with constraint (string.string) disabled and validated
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-07248 : sfwfb: write error, unable to write database block.
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-27037 : unable to obtain file status
  • ora-37152 : MDX query error: (string)
  • ora-26731 : %s 'string' does not exist
  • ora-25408 : can not safely replay call
  • ora-38785 : Media recovery must be enabled for guaranteed restore point.
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-24008 : queue table string.string must be dropped first
  • ora-12810 : PARALLEL_MAX_SERVERS must be less than or equal to string
  • ora-12413 : labels do not belong to the same policy
  • ora-29953 : cannot issue DDL on a domain index partition marked as FAILED
  • ora-25133 : duplicate SINGLE TABLE option specified
  • ora-00307 : requested INSTANCE_NUMBER out of range, maximum is string
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-12200 : TNS:could not allocate memory
  • ora-02164 : DATAFILE clause specified more than once
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-25509 : operation on "string"."string".string not allowed
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-19380 : invalid plan filter
  • ora-15125 : ASM file name 'string' contains an invalid template name
  • ora-23436 : missing template authorization for user
  • ora-08413 : invalid compiler type in FORMAT parameter at string
  • ora-02055 : distributed update operation failed; rollback required
  • 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.