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 : 26-07-2017

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-29833 : indextype does not exist
  • ora-31221 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd.
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-36665 : (XSDPART03) workspace object is not in the dimension list of the PARTITION TEMPLATE.
  • ora-02025 : all tables in the SQL statement must be at the remote database
  • ora-28538 : result set not found
  • ora-29970 : Specified registration id does not exist
  • ora-02789 : Maximum number of files reached
  • ora-24366 : migratable user handle is set in service handle
  • ora-01663 : the contents of tablespace 'string' is constantly changing
  • ora-30394 : source statement identical to the destination statement
  • ora-07578 : szprv: $FIND_HELD failure
  • ora-32841 : invalid value for property string
  • ora-28668 : cannot reference mapping table of an index-organized table
  • ora-40002 : wordsize must be string or greater
  • ora-27469 : %s is not a valid string attribute
  • ora-13622 : invalid recommendation annotation
  • ora-15116 : invalid combination of ALTER DISKGROUP options
  • ora-32738 : Hang analysis aborted due to failed memory copy
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-15092 : I/O request size string is not a multiple of logical block size string
  • ora-01116 : error in opening database file string
  • ora-19767 : missing TRACKING keyword
  • ora-13373 : invalid line segment in geodetic data
  • ora-01411 : cannot store the length of column in the indicator
  • ora-24157 : duplicate variable name string
  • ora-13856 : Service name must be specified
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-24433 : This statement has already been prepared using OCIStmtPrepare2.
  • ora-01913 : EXCLUSIVE keyword expected
  • 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.