ORA-00278: log file 'string' no longer needed for this recovery

Cause : The specified redo log file is no longer needed for the current recovery.

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

No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.

update : 20-09-2017
ORA-00278

ORA-00278 - log file 'string' no longer needed for this recovery
ORA-00278 - log file 'string' no longer needed for this recovery

  • ora-31507 : %s parameter value longer than maximum length string
  • ora-24372 : invalid object for describe
  • ora-15152 : cluster in rolling upgrade
  • ora-27002 : function called with invalid device structure
  • ora-07843 : sllfcl: LIB$FREE_VM failure
  • ora-31445 : invalid lock handle while acquiring lock on string
  • ora-09351 : Windows 32-bit Two-Task driver unable to allocate shared memory
  • ora-39061 : import mode string conflicts with export mode string
  • ora-02182 : savepoint name expected
  • ora-19271 : XP0051 - invalid atomic type definition
  • ora-29525 : referenced name is too long: 'string'
  • ora-30373 : object data types are not supported in this context
  • ora-16115 : %s\% of LogMiner dictionary loading is done
  • ora-12702 : invalid NLS parameter string used in SQL function
  • ora-12446 : Insufficient authorization for administration of policy string
  • ora-25122 : Only LOCAL bitmap indexes are permitted on partitioned tables
  • ora-08120 : Need to create SYS.IND_ONLINE$ table in order to (re)build index
  • ora-01294 : error occurred while processing information in dictionary file string, possible corruption
  • ora-21779 : duration not active
  • ora-22955 : The cardinality parameter is not within the allowed limits
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • ora-39773 : parse of metadata stream failed
  • ora-09765 : osnmop: fork failed
  • ora-31515 : CDC change source string already exists
  • ora-14031 : partitioning column may not be of type LONG or LONG RAW
  • ora-16547 : cannot disable the primary database
  • ora-39039 : Schema expression "string" contains no valid schemas.
  • ora-16710 : the resource guard is out of memory
  • ora-01160 : file is not a string
  • ora-32580 : both SYS and SYSTEM passwords must be provided
  • 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.