Oracle Data recovery: Error stacking leads to disaster unrecoverable solutions

When the customer first came to me, I told him to give us the hard drive and we could get the data back.
The next day the client said that the hard drive was formatted to redo the system.

When the customer came to me for the second time, I said, give me the remaining three files, and I can help you save the useful data.
The next day the client said that the backup had been taken and the three files were flushed.

This story gives us the alert is: Backup, Backup, backup, and more than one more; fault handling, plus 10,000 more caution is not much.

The first simple failure, after a layer of error, is completely irreversible, and this is the most dramatic recovery case I've seen in years.

Take a look at this breakdown, first of all, a write error, a typical and common storage access error in Windows:

The code is as follows

Copy Code

Sat Sep 23 18:44:51 2011 Kcf:write/open Error block=0x35673a online=1 Sat Sep 23 18:44:51 2011 Kcf:write/open Error BLOCK=0X25EBA4 online=1 file=124 D:DTAPRODTA02. Dbf error=27070 txt: ' OSD-04016: An error occurred while the asynchronous I/O request queued. O/s-error: (OS 2) The system could not find the specified file. ' Ora-01242:data file suffered media failure:database in Noarchivelog mode Ora-01114:io Error writing block to file 124 (Block # 24856) Ora-01110:data file 124: ' D:dtaprodta02. DBF ' Ora-27070:skgfdisp:async Read/write failed OSD-04016: An error occurred while waiting for an asynchronous I/O request. O/s-error: (OS 2) The system could not find the specified file.

Then, the recovery uses a April backup and covers the saved files:

code is as follows	copy code
sun Sep 24 20:58:32 The input backup piece G:BCKDB_T20110421_S111_P1 is in compressed format.