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-04-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-03113 : end-of-file on communication channel
  • ora-22287 : invalid or modified directory occurred during string operation
  • ora-09770 : pws_look_up: translation failure.
  • ora-08414 : error encountered in string
  • ora-25247 : %s is not a recipient of specified message
  • ora-26716 : message limit reached
  • ora-39057 : invalid worker request string for string jobs.
  • ora-22893 : constraint can be specified only for REF columns
  • ora-02799 : Unable to arm signal handler
  • ora-16161 : Cannot mix standby and online redo log file members for group string
  • ora-36223 : (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type
  • ora-30075 : TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
  • ora-13616 : The current user string has not been granted the ADVISOR privilege.
  • ora-07244 : ssfccf: create file failed, file size limit reached.
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-19006 : XMLType TYPE storage option not appropriate for storage type
  • ora-16727 : resource guard cannot close database
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-12924 : tablespace string is already in force logging mode
  • ora-25121 : MINIMUM EXTENT value greater than maximum extent size
  • ora-12012 : error on auto execute of job string
  • ora-13060 : topology with the name string already exists
  • ora-31079 : unable to resolve reference to string "string"
  • ora-15014 : location 'string' is not in the discovery set
  • ora-00977 : duplicate auditing option
  • ora-07568 : slspool: $OPEN failure
  • ora-13460 : GeoRaster metadata SRS error
  • ora-09889 : osnTXtt: access error on oracle executable
  • ora-31083 : error while creating SQL type "string"."string"
  • ora-06911 : CMX: t_event returns ERROR
  • 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.