March 11, 2009 at 1:57 pm
Hi All,
During the upgrade on a DB I got the error below.
SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xffffffff; actual signature: 0x55555557). It occurred during a read of page (1:4695) in database ID 8 at offset 0x000000024ae000 in file
'D:\XceleraDatabase\MSSQL.1\MSSQL\Xc12_XceleraData.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately.
Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Should I try to restore the DB from the Backup?
Thanks
Shallu
March 11, 2009 at 2:08 pm
You'll need to fix this before upgrading, using the method that gives you the smallest amount of downtime and data-loss (whichever is more important to you).
Did you have a power outage recently that could have led to this?
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
March 11, 2009 at 2:20 pm
No, there was no power outage. The error came up during the data migration.
March 11, 2009 at 2:48 pm
ok, but this is an error caused by IO subsystems, not SQL Server. One of the IO subsystems involved had a problem that caused this. Can you run the following on the pre-upgrade database:
DBCC CHECKDB (yourdb) WITH ALL_ERRORMSGS, NO_INFOMSGS
and post the results here.
What upgrade are you performing?
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply