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 : 27-04-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-10580 : Can not modify datafile header during test recovery
  • ora-01571 : redo version string incompatible with ORACLE version string
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-31409 : one or more values for input parameters are incorrect
  • ora-15012 : ASM file 'string' does not exist
  • ora-30066 : test support - drop rollback segment wait
  • ora-31095 : cannot generate string : "string.string" already exists
  • ora-22997 : VARRAY | OPAQUE stored as LOB is not specified at the table level
  • ora-08274 : Out of memory for environment variable
  • ora-00150 : duplicate transaction ID
  • ora-12157 : TNS:internal network communication error
  • ora-03282 : missing ALLOCATE EXTENT option
  • ora-01208 : data file is an old version - not accessing current version
  • ora-37037 : (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
  • ora-29376 : number of consumer groups string in top-plan string exceeds string
  • ora-00273 : media recovery of direct load data that was not logged
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-01929 : no privileges to GRANT
  • ora-00251 : LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string
  • ora-25264 : cant get signature for this queue
  • ora-16540 : invalid argument
  • ora-30031 : the suspended (resumable) statement has been aborted
  • ora-29896 : Length of PARAMETER string longer than string characters
  • ora-02833 : Server was unable to close file
  • ora-12673 : Dedicated server: context not saved
  • ora-13791 : cannot resume a tuning task created to tune a single statement
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-30396 : rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-13137 : failed to generate tablespace sequence number
  • 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.