ORA-10580: Can not modify datafile header during test recovery

Cause : To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers.

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

No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.

update : 21-08-2017
ORA-10580

ORA-10580 - Can not modify datafile header during test recovery
ORA-10580 - Can not modify datafile header during test recovery

  • ora-29960 : line string, string
  • ora-06010 : NETASY: dialogue file too long
  • ora-24409 : client cannot understand the object
  • ora-12704 : character set mismatch
  • ora-10360 : enable dbwr consistency checking
  • ora-24003 : Queue table index string inconsistent with queue table string
  • ora-16406 : Primary and standby database software version mismatch
  • ora-26103 : V6 or V7 data file used to create control file
  • ora-00328 : archived log ends at change string, need later change string
  • ora-12406 : unauthorized SQL statement for policy string
  • ora-28165 : proxy 'string' may not specify password-protected role 'string' for client 'string'
  • ora-12219 : TNS:missing community name from address in ADDRESS_LIST
  • ora-16204 : DDL successfully applied
  • ora-36271 : (XSCGMDLAGG11) workspace object is not in the dimension list of valueset workspace object.
  • ora-14125 : REVERSE/NOREVERSE may not be specified in this context
  • ora-13339 : LRS polygon clipping across multiple rings
  • ora-02075 : another instance changed state of transaction string
  • ora-19653 : cannot switch to older file incarnation
  • ora-24365 : error in character conversion
  • ora-16547 : cannot disable the primary database
  • ora-22906 : cannot perform DML on expression or on nested table view column
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-13763 : illegal ranking attribute "string"
  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-19715 : invalid format string for generated name
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-37113 : OLAP API initialization error: (string)
  • ora-25260 : AQ latch cleanup testing event
  • 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.