Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chaithanya
Starting Member
17 Posts |
 Posted - 2005-07-13 : 09:39:16
|
| 1. When i select the table(XXXXX_header) in pomdb using Query Analyzer it throws the error Server: Msg 823, Level 24, State 2, Line 1I/O error (bad page ID) detected during read at offset 0x00000000862000 in file 'E:\DATABASE\POMDEV.mdf'. Connection Broken2.dbcc checkdb('pomdb') Result: Server: Msg 8966, Level 16, State 1, Line 1Could not read and latch page (1:1073) with latch type SH. sysindexes failed.DBCC execution completed. If DBCC printed error messages, contact your system administrator.We use SQL 2K SP3a on Windows NT4 SP6Chaithanya J |
|
|
franco
Constraint Violating Yak Guru
255 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-07-13 : 13:02:35
|
| Try dropping and recreating the indexes. If that doens't work, check out the different repair options in the DBCC CHECKDB command.Tara |
 |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-07-13 : 15:16:33
|
quote:
Originally posted by tduggan
Try dropping and recreating the indexes. If that doens't work, check out the different repair options in the DBCC CHECKDB command.Tara
Its a bad page in sysindexes - actually a bad page on the disk so you have hardware problems. SQL Server can't repair this page so you have no choice but to restore from backup or extract the data into a new db on different hardware.Paul RandalDev Lead, Microsoft SQL Server Storage Engine |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-07-13 : 15:17:51
|
| What I should have said is that SQL Server can't repair this page because its in sysindexes. For most 823s, it will deallocate the page during repair and you can carry on using the bad hardware until you get more 823s, ad infinitum.Paul RandalDev Lead, Microsoft SQL Server Storage Engine |
|
|
|
chaithanya
Starting Member
17 Posts |
Posted - 2005-07-14 : 01:29:55
|
| Thank you all! You mean to say ther's a problem with the hardware. ok. And what i did here is it was a Master table. I dropped it and created a new one. It's ok for now. Now my question is - What happened to that bad page after the table is dropped? Is there a possibilty of SQL Server using that bad page again?Thank you..Chaithanya J |
|
|
|
franco
Constraint Violating Yak Guru
255 Posts |
|
|
|
|
|
|
|
I/O error 823 - bad page ID