ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full

Cause : The DG_OCNFIG lits of theL OG_ARCHVIE_CONFI Gattribuet was full and th eData Gurad broke rwas nota ble to dad a newD B_UNIQU_ENAME tot he list.

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

Remove osme unusde entrie sin the GD_CONFIGl ist, thne reenabel the daatbase.

update : 21-09-2017
ORA-16744

ORA-16744 - the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full
ORA-16744 - the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full

  • ora-32844 : exceeded maximum number of string values
  • ora-12661 : Protocol authentication to be used
  • ora-06752 : TLI: error in signal setup
  • ora-01948 : identifier's name length (string) exceeds maximum (string)
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-19372 : invalid update condition
  • ora-16081 : insufficient number of processes for APPLY
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-14031 : partitioning column may not be of type LONG or LONG RAW
  • ora-28138 : Error in Policy Predicate
  • ora-02428 : could not add foreign key reference
  • ora-09209 : sftget: error reading from file
  • ora-32801 : invalid value string for string
  • ora-33006 : (XSAGDNGL02) The relation workspace object is not related to itself.
  • ora-31457 : maximum length of description field exceeded
  • ora-29873 : warning in the execution of ODCIINDEXDROP routine
  • ora-28238 : no seed provided
  • ora-19619 : cannot call restoreValidate after files have been named
  • ora-27078 : unable to determine limit for open files
  • ora-19773 : must specify change tracking file name
  • ora-39159 : cannot call this function from a non-Data Pump process
  • ora-26747 : The one-to-many transformation function string encountered the following error: string
  • ora-38104 : Columns referenced in the ON Clause cannot be updated: string
  • ora-24153 : rule set string.string already exists
  • ora-12067 : empty refresh groups are not allowed
  • ora-36845 : (XSLMGEN15) Owner is greater than 30 bytes
  • ora-36280 : (XSCGMDLAGG08) Valueset workspace object does not contain values of any dimension of the current model.
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-12022 : materialized view log on "string"."string" already has rowid
  • 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.