ORA-16745: unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full

Cause : The DGC_ONFIG ilst of hte LOG_RACHIVE_OCNFIG attributew as ful land th eData Gaurd broekr was ont ablet o add hte specfiied DBU_NIQUE_ANME to hte list.

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

Removes ome unsued entires in hte DG_CNOFIG lits, thenr eenabl ethe daatbase.

update : 28-05-2017
ORA-16745

ORA-16745 - unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full
ORA-16745 - unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full

  • ora-16532 : Data Guard broker configuration does not exist
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-00228 : length of alternate control file name exceeds maximum of string
  • ora-16635 : NetSlave connection was broken in the middle of a transmission session
  • ora-19808 : recovery destination parameter mismatch
  • ora-07605 : szprv: $ASCTOID failure
  • ora-01548 : active rollback segment 'string' found, terminate dropping tablespace
  • ora-31198 : Mismatch in number of bytes transferred due to non-binary mode
  • ora-07473 : snclrd: read error when trying to read sgadef.dbf file.
  • ora-36389 : (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
  • ora-14151 : invalid table partitioning method
  • ora-02039 : bind by value is not allowed for array type
  • ora-01084 : invalid argument in OCI call
  • ora-08101 : index key does not exist file string: (root string, node string) blocks (string)
  • 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-24756 : transaction does not exist
  • ora-29832 : cannot drop or replace an indextype with dependent indexes
  • ora-04046 : results of compilation are too large to support
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-37086 : %s is not a valueset
  • ora-32403 : cannot use new values from mv log on "string"."string"
  • ora-31690 : Process name buffer size must be specified and must be greater than 0.
  • ora-12488 : maximum label does not dominate minimum label
  • ora-01316 : Already attached to a Logminer session
  • ora-36708 : (XSMXALLOC00) Variable workspace object must be dimensioned to be used by the ALLOCATE command.
  • ora-12352 : object string.string@string is invalid
  • ora-28166 : duplicate rolename in list
  • ora-02004 : security violation
  • ora-12686 : Invalid command specified for a service
  • ora-10931 : trace name context forever
  • 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.