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 : 25-04-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-07212 : slcpu: times error, unable to get cpu time.
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-40201 : invalid input parameter string
  • ora-19701 : device name exceeds maximum length of string
  • ora-19323 : Invalid url string
  • ora-16219 : This database is not preparing to switch over.
  • ora-00254 : error in archive control string 'string'
  • ora-30101 : unknown parameter name 'string'
  • ora-27378 : cannot stop jobs of type EXECUTABLE on this platform
  • ora-37069 : You may not execute a parallel OLAP operation against the EXPRESS AW.
  • ora-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-15173 : entry 'string' does not exist in directory 'string'
  • ora-07596 : sptpa: $GETJPIW failure
  • ora-26670 : STREAMS option requires COMPATIBLE parameter to be string or higher
  • ora-39133 : object type "string"."string" already exists with different typeid
  • ora-31422 : owner schema string does not exist
  • ora-06556 : the pipe is empty, cannot fulfill the unpack_message request
  • ora-16630 : that database property was deprecated
  • ora-22626 : Type Mismatch while constructing or accessing OCIAnyData
  • ora-37027 : (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-14451 : unsupported feature with temporary table
  • ora-12481 : effective label not within program unit clearance range
  • ora-06317 : IPA: Local maximum number of users exceeded
  • ora-13412 : invalid scale parameter
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-12557 : TNS:protocol adapter not loadable
  • ora-22628 : OCIAnyData already constructed
  • ora-08231 : smscre: unable to attach to SGA
  • ora-27488 : unable to set string because string was/were already set
  • 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.