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 : 20-09-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-16952 : Failed to bind this SQL statement.
  • ora-36273 : (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR.
  • ora-29315 : tablespace 'string' has been recreated
  • ora-29320 : datafile header error
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-30446 : valid workload queries not found
  • ora-26663 : error queue for apply process string must be empty
  • ora-13189 : recursive SQL parse failed
  • ora-15101 : no action specified
  • ora-02835 : Server unable to send signal to client
  • ora-15155 : version incompatible with the cluster
  • ora-24185 : transformation string.string does not exist
  • ora-39707 : compatibile parameter string too high for downgrade to string
  • ora-15130 : diskgroup "string" is being dismounted
  • ora-04083 : invalid trigger variable 'string'
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-02838 : Unable to arm signal handler for the alarm signal
  • ora-31665 : mode can only be defaulted for IMPORT and SQL_FILE operations
  • ora-13243 : specified operator is not supported for 3- or higher-dimensional R-tree
  • ora-09750 : pw_attachPorts: port_rename failed.
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-30933 : Element 'string' may not appear at this point within parent 'string'
  • ora-39171 : Job is experiencing a resumable wait. string
  • ora-13461 : the interleaving type is not supported
  • ora-28035 : Cannot Get Session Key for Authentication
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-31180 : DOM Type mismatch in invalid PL/SQL DOM handle
  • ora-26668 : STREAMS process string exists
  • ora-10660 : Segment is a shared lob segment
  • 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.