Hi everyone. I have a data warehouse that I've been using for about 6 months, and I update it weekly. It has about 30 tables, including a data staging area, 2 fact tables, numerous dimension tables and some processing tables. It's been working great, and I've been making small incremental improvements to the product, with the occasional addition of a DTS package, stored procedure or table here and there.
This past week I've been plagued by an error that will now allow me to update the warehouse. 2 of my tables that have been in use for months now have the following message when I run the 'DBCC CHECKDB' sproc:
DBCC results for 'T_Fact.'
"Server: Msg 8909, Level 16, State1, Line1
Table error: Object ID 155147598, index ID0, page ID(1:668083). The Page ID in the page header =(1:668074).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 166146587, index ID0: Page(1:668083) Could not be processed. See other errors for details.
.
.
. (there are 3 other sets of these 2 errors, each with a different page id)
.
.
CHECKDB found 0 allocation errors and 22 consistency errors in the table 'T_Fact' (object ID 155147598).
The calling program's log produces the following message after the app stops with an error:
[Microsoft] [ODBC SQL Server Driver] [SQL Server] I/O error (bad page ID) detected during read at offset 0x0000009E9CC000 in file 'E:\MSSQL\Data\DbName_Data.MDF'.
Running the stored procedure that it locks up on produces a smiliar error.
There is also a lightly used dimension table that has the same info as above. I've tried dropping and rebuilding the table which seemed to work the first time, but now it doesn't work either.
Any ideas? Do I have a bad operating system install or SQL Server 2000 install? Rebooting, destroying and recreating the table, and changing the order of the procedure calls hasn't helped. I'm looking at some nonsensical ideas like changing my code, detaching and reattaching, and possibly reinstalling the operating system and applications. Any help and/or ideas would be greatly appreciated.
Thanks!
This past week I've been plagued by an error that will now allow me to update the warehouse. 2 of my tables that have been in use for months now have the following message when I run the 'DBCC CHECKDB' sproc:
DBCC results for 'T_Fact.'
"Server: Msg 8909, Level 16, State1, Line1
Table error: Object ID 155147598, index ID0, page ID(1:668083). The Page ID in the page header =(1:668074).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 166146587, index ID0: Page(1:668083) Could not be processed. See other errors for details.
.
.
. (there are 3 other sets of these 2 errors, each with a different page id)
.
.
CHECKDB found 0 allocation errors and 22 consistency errors in the table 'T_Fact' (object ID 155147598).
The calling program's log produces the following message after the app stops with an error:
[Microsoft] [ODBC SQL Server Driver] [SQL Server] I/O error (bad page ID) detected during read at offset 0x0000009E9CC000 in file 'E:\MSSQL\Data\DbName_Data.MDF'.
Running the stored procedure that it locks up on produces a smiliar error.
There is also a lightly used dimension table that has the same info as above. I've tried dropping and rebuilding the table which seemed to work the first time, but now it doesn't work either.
Any ideas? Do I have a bad operating system install or SQL Server 2000 install? Rebooting, destroying and recreating the table, and changing the order of the procedure calls hasn't helped. I'm looking at some nonsensical ideas like changing my code, detaching and reattaching, and possibly reinstalling the operating system and applications. Any help and/or ideas would be greatly appreciated.
Thanks!
