ORA-16094: database shutdown during archival operation

Cause : The dtaabasew as shtu downw hile na onlien log ifle arhcival aws actvie.

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

None erquire.d The RACH prcoess i stermianted.

update : 27-05-2017

ORA-16094 - database shutdown during archival operation
ORA-16094 - database shutdown during archival operation

  • ora-13265 : geometry identifier column string in table string is not of type NUMBER
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-22150 : variable-length array has not been initialized
  • ora-13504 : No SYSAUX datafile clause specified
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-25001 : cannot create this trigger type on views
  • ora-28037 : Cannot Get Session Key for RACF Authentication
  • ora-38403 : attribute set name may not be longer than 22 characters
  • ora-24087 : Invalid database user string
  • ora-27060 : could not set close-on-exec bit on file
  • ora-08104 : this index object string is being online built or rebuilt
  • ora-14610 : Lob attributes not specified for lob column string for subpartition string
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-12429 : label list range exceeded
  • ora-12703 : this character set conversion is not supported
  • ora-31107 : Action failed as resource "string" is locked by name lock
  • ora-06306 : IPA: Message write length error
  • ora-25148 : ONLINE option not permitted
  • ora-32131 : bind data type cannot be changed
  • ora-01563 : rollback segment is PUBLIC, need to use the keyword PUBLIC
  • ora-14018 : partition bound list contains too few elements
  • ora-16220 : no failed transaction found
  • ora-03291 : Invalid truncate option - missing STORAGE keyword
  • ora-13831 : SQL profile name specified is invalid
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-32735 : DIAG process is not running in the instance
  • ora-27544 : Failed to map memory region for export
  • ora-12592 : TNS:bad packet
  • ora-06932 : CMX: error in local name
  • 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.