torn pages and bad page ID 
Author Message
 torn pages and bad page ID

I'm running SQL 2000 on a Windows 2000 SP3 machine.  This is setup as
a failover cluster.  I recently applied SQL Server's SP3.  (I had been
running SP2 before hand.)  Two days later, I started getting the
following errors:

##################
Error: 823, Severity: 24, State: 2
I/O error (torn page) detected during read at offset 0x000003384ea000
in file 'G:\Program Files\Microsoft SQL
Server\MSSQL\Data\ae_commerce.mdf'.

Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset
0x0000033c54e000 in file 'G:\Program Files\Microsoft SQL
Server\MSSQL\Data\ae_commerce.mdf'..
###################

On top of that, I keep getting indices corrupted.  I rebuild them, but
they continue to go bad.  I'm thinking it's related to the above
errors:

#####################
Table error: Database ID 7, object ID 613629279, index ID 0. Chain
linkage mismatch. (1:1655362)->next = (1:1640461), but
(1:1640461)->prev = (1:1655363)..
#####################

The only thing that's changed on the clustered boxes in 4 months is I
applied SQL's SP3.  Any chance the service pack is hosing my database?



Mon, 15 Aug 2005 22:27:56 GMT
 torn pages and bad page ID

I am not aware of any issues regarding torn pages and SP3. I *have* seen
cases where, in a cluster failover, torn pages can result from switching the
disks while a write is in progress.
--
Eric Christensen
SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.

Quote:
> I'm running SQL 2000 on a Windows 2000 SP3 machine.  This is setup as
> a failover cluster.  I recently applied SQL Server's SP3.  (I had been
> running SP2 before hand.)  Two days later, I started getting the
> following errors:

> ##################
> Error: 823, Severity: 24, State: 2
> I/O error (torn page) detected during read at offset 0x000003384ea000
> in file 'G:\Program Files\Microsoft SQL
> Server\MSSQL\Data\ae_commerce.mdf'.

> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset
> 0x0000033c54e000 in file 'G:\Program Files\Microsoft SQL
> Server\MSSQL\Data\ae_commerce.mdf'..
> ###################

> On top of that, I keep getting indices corrupted.  I rebuild them, but
> they continue to go bad.  I'm thinking it's related to the above
> errors:

> #####################
> Table error: Database ID 7, object ID 613629279, index ID 0. Chain
> linkage mismatch. (1:1655362)->next = (1:1640461), but
> (1:1640461)->prev = (1:1655363)..
> #####################

> The only thing that's changed on the clustered boxes in 4 months is I
> applied SQL's SP3.  Any chance the service pack is hosing my database?



Tue, 16 Aug 2005 02:03:47 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. Attaching a damaged database - I/O error (bad page ID) detected during read

2. URGENT : Error Message 823 - bad page id

3. How to recover from I/O error (bad page ID) detected

4. Error 823 -I/O error- bad page ID

5. I/O error (bad page ID) detected during read of BUF pointer = 0x11bde680

6. I/O error (bad page ID) detected during read

7. I/O error (bad page ID) detected during read of BUF pointer

8. I/O error (bad page ID) detected

9. I/O error (bad page ID) detected during read of BUF pointer

10. Error 823 I/O error (bad page ID)....

11. I/O error (bad page ID)

12. Torn Page


 
Powered by phpBB® Forum Software