The document details the process of restoring data to a customer. The cause is that the disaster cannot be recovered due to missuperposition.
The document details the process of restoring data to a customer. The cause is that the disaster cannot be recovered due to missuperposition.
The document details the process of restoring data to a customer. The cause is that the disaster cannot be recovered due to missuperposition.
When the customer first asked me for help, I told him that we could recover the data by bringing the hard disk to us.
The next day, the customer said that the hard disk was formatted and redone to the system.
When the customer asked me for the second time, I said, "Give me the remaining three files, and I can help you save the remaining useful data.
The next day, the customer said that the backup had been used to refresh and overwrite the three files.
This story provides us with the warning that backup, and more than one copy are not too much. troubleshooting, plus 10 thousand pieces of caution is not much.
An initial simple fault was completely irrecoverable after a layer-by-layer error. This is the most dramatic recovery case I have seen over the years.
Take a look at the fault information. The first is a write error. Typical and common storage access errors in Windows:
The Code is as follows: |
|
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: 'oss-04016: An error occurred while queuing asynchronous I/O requests. O/S-Error: (OS 2) the system cannot 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 queuing asynchronous I/O requests. O/S-Error: (OS 2) the system cannot find the specified file. |
Then, I used a backup in January and overwritten the saved files:
The Code is as follows: |
|
Sun Sep 24 20:58:32 2011 The input backup piece G: bckdb_t20151121_s111_p1 is in compressed format. |