Mon Jan 14 00:09:42 2015 MMNL started with pid=16, OS id=14990 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = /u01/app/oracle Mon Jan 14 00:09:42 2015 ALTER DATABASE MOUNT Set as converted control file due to db_unique_name mismatch Changing di2dbun from to orcl Successful mount of redo thread 1, with mount id 1434172742 Database mounted in Exclusive Mode Lost write protection disabled Create Relation IPS_PACKAGE_UNPACK_HISTORY Completed: ALTER DATABASE MOUNT Mon Jan 14 00:10:13 2015 alter database open Errors in file /u01/app/oracle/oradata/orcl/diag/rdbms/orcl/orcl/trace/orcl_ora_15080.trc: ORA-01589: must use RESETLOGS or NORESETLOGS option for database open ORA-1589 signalled during: alter database open... Mon Jan 14 00:10:26 2015 ALTER DATABASE RECOVER database using backup controlfile until cancel Media Recovery Start Serial Media Recovery started WARNING! Recovering data file 1 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 2 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 3 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 4 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 5 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. WARNING! Recovering data file 6 from a fuzzy file. If not the current file it might be an online backup taken without entering the begin backup command. ORA-279 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ... ALTER DATABASE RECOVER CONTINUE DEFAULT Media Recovery Log /u01/app/oracle/flash_recovery_area/ORCL/archivelog/2015_03_14/o1_mf_1_2_%u_.arc Errors with log /u01/app/oracle/flash_recovery_area/ORCL/archivelog/2015_03_14/o1_mf_1_2_%u_.arc ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ... ALTER DATABASE RECOVER CANCEL ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ... Mon Jan 14 00:10:29 2015 Checker run found 7 new persistent data failures Mon Jan 14 00:10:47 2015 alter database open resetlogs RESETLOGS is being done without consistancy checks. This may result in a corrupted database. The database should be recreated. RESETLOGS after incomplete recovery UNTIL CHANGE 67619908 Online log /u01/app/oracle/soft/orcl/REDO03.LOG: Thread 1 Group 3 was previously cleared Mon Jan 14 00:10:53 2015 ... Hex dump of (file 1, block 3273) in trace file /u01/app/oracle/oradata/orcl/diag/rdbms/orcl/orcl/trace/orcl_ora_15080.trc Corrupt block relative dba: 0x00400cc9 (file 1, block 3273) Bad header found during buffer read Data in bad block: type: 255 format: 7 rdba: 0xffffffff last change scn: 0xffff.ffffffff seq: 0xff flg: 0xff spare1: 0xff spare2: 0xff spare3: 0xffff consistency value in tail: 0x43830601 check value in block header: 0xffff computed block checksum: 0x446e Reading datafile '/u01/app/oracle/soft/orcl/SYSTEM01.DBF' for corruption at rdba: 0x00400cc9 (file 1, block 3273) Reread (file 1, block 3273) found same corrupt data Mon Jan 14 00:10:54 2015 Hex dump of (file 2, block 72411) in trace file /u01/app/oracle/oradata/orcl/diag/rdbms/orcl/orcl/trace/orcl_p000_15112.trc Corrupt block relative dba: 0x00811adb (file 2, block 72411) Bad header found during buffer read Data in bad block: type: 255 format: 7 rdba: 0xffffffff last change scn: 0xffff.ffffffff seq: 0xff flg: 0xff spare1: 0xff spare2: 0xff spare3: 0xffff consistency value in tail: 0x3ce30608 check value in block header: 0xffff computed block checksum: 0xfe3c Reading datafile '/u01/app/oracle/soft/orcl/SYSAUX01.DBF' for corruption at rdba: 0x00811adb (file 2, block 72411) Reread (file 2, block 72411) found same corrupt data Errors in file
I have reviewed the alert log and I see the database is finding serious issues.
This is a physical corruption and considering we have it also in file 1, there are probably bootstrap objects.
Do you have any backup for this database? If yes, please proceed with restore/recovery operations.
Otherwise, the information in the blocks is lost and with the errors reported and previous actions of the database, I am not sure if any option to open it.
I have no any backup on this database.
With no backup, the last resort was to force open the database, which was already attempted.
This didn’t work as we have affected a bootstrap object.
Unless the database can be recreated from other source, PRM-DUL (Data recovery UnLoaderhttp://www.parnassusdata.com/en) might be used to scan a database file, recognize table header blocks, access extent information, and read all rows.
It places the unloaded data into a flat file to be subsequently loaded back into a database.
TRY PRM-DUL http://www.parnassusdata.com/en