ORA-16014: log string sequence# string not archived, no available destinations

Cause : An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.

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

Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.

update : 25-09-2017
ORA-16014

ORA-16014 - log string sequence# string not archived, no available destinations
ORA-16014 - log string sequence# string not archived, no available destinations

  • ora-19246 : XQ0026 - validation failed - element string not found in in-scope element declarations
  • ora-15018 : diskgroup cannot be created
  • ora-39115 : %s is not supported over a network link
  • ora-14066 : illegal option for a non-partitioned index-organized table
  • ora-23321 : Pipename may not be null
  • ora-31194 : Resource string is already deleted
  • ora-39156 : error parsing dump file name "string"
  • ora-31213 : DBMS_LDAP: PL/SQL - Invalid LDAP mod option.
  • ora-28560 : error in configuration of agent process
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-01841 : (full) year must be between -4713 and +9999, and not be 0
  • ora-22905 : cannot access rows from a non-nested table item
  • ora-38749 : A media recovery has been started.
  • ora-12715 : invalid character set specified
  • ora-14288 : index is not partitioned by Composite Range method
  • ora-14602 : SUBPARTITION TEMPLATE is legal only for a composite partitioned table
  • ora-22810 : cannot modify object attributes with REF dereferencing
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-01107 : database must be mounted for media recovery
  • ora-09271 : szlon: error verifying user name
  • ora-01530 : a database already mounted by the instance
  • ora-09764 : osnmop: access error on oracle executable
  • ora-07596 : sptpa: $GETJPIW failure
  • ora-14501 : object is not partitioned
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-16714 : the value of property string is inconsistent with the database setting
  • ora-31027 : Path name or handle string does not point to a resource
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-00151 : invalid transaction ID
  • ora-21603 : property id [string] is invalid
  • 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.