01.27.06
SQL Error: I/O error 1450 (error not found)
The past 3 days were nightmare. All the application on one of business database stopped working. After hours of debugging, I locate this error from SQL Server. There are not many information on the Internet, and I could not look it up from MSDN website. It looks like some I/O error with database file.
I run “DBCC CHECKDB” and found many torn pages and other errors. Because the database is relatively big, the error does not appear all the time. After several rollback, I found these errors have been hidden in my database for a while. I did not encounter them because the applications did not access these data before. Sadly, I have rollback old backup day by day, until I found a day that DBCC CHECK will not report any errors.
This is really time consuming work, and I have spent 2 days to finally get the latest error free backup. After that, I have manually extract differential data from corrupted database to the backup restore. However, this attemp becomes a hassle because I found that after I copied certain data over to the new database, the torn pages will show up again. =( Since I moved these information in batches of million, it is impossible for me to locate the problem unless I get more deep in physical records, which I feel it is not worth the time.
After 3 days of work, I finally get all application back online with loss of some recent data. However, I am still watching it closely, in case the error will show up again. Now I understand why companies are paying so much dollars to a good DBA.
The lesson I learn: Run DBCC CHECK and backup regularly. The errors can hide in a large database for a long time.