|
Home > Archive > MS SQL Server > May 2005 > Torn page detected but can't find problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Torn page detected but can't find problem
|
|
|
| We received an alert this morning "I/O error (torn page) detected during read
at offset 0x0000000203c000 in file 'd:\data\data\CFS_Da
ta.MDF"
then about 20 minutes later, "I/O error (bad page ID) detected during read
at offset 0x0000000203e000 in file 'd:\data\data\CFS_Da
ta.MDF'.."
There are no error messages in the system event viewer of the server. I ran
dbcc checkdb and no errors returned, I also ran dbcc dropcleanbuffers and
hten dbcc checkdb however no errors are reported. The database is also not
labeled suspect. I'm not sure what to do at this point since I can't find a
problem. I read that this error can often occur when power is lost and we
did lost power last weekend and the our ups went down as well however we
received no errors like this until today.
Any advice?
- Steve
| |
| Wayne Snyder 2005-05-29, 9:23 am |
| Perhaps you need to open a call to PSS... but..
You have the page number and file name... From that you can use DBCC Page,
to discover the object the page belongs to...
If it is a nonclustered index, simply rebuild the index... Otherwise you may
need PSSs help any way to drop the page from the chain...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Steve" <Steve@discussions.microsoft.com> wrote in message
news:2281BB5B-E373-4349-B8E1- 6FBCDC92FA60@microso
ft.com...
> We received an alert this morning "I/O error (torn page) detected during
> read
> at offset 0x0000000203c000 in file 'd:\data\data\CFS_Da
ta.MDF"
> then about 20 minutes later, "I/O error (bad page ID) detected during read
> at offset 0x0000000203e000 in file 'd:\data\data\CFS_Da
ta.MDF'.."
>
> There are no error messages in the system event viewer of the server. I
> ran
> dbcc checkdb and no errors returned, I also ran dbcc dropcleanbuffers and
> hten dbcc checkdb however no errors are reported. The database is also
> not
> labeled suspect. I'm not sure what to do at this point since I can't find
> a
> problem. I read that this error can often occur when power is lost and we
> did lost power last weekend and the our ups went down as well however we
> received no errors like this until today.
>
> Any advice?
> - Steve
|
|
|
|
|