Newbie-Page Torn Detection - ambigious results

Hi All,
I had a database tornpage detected and at traced the table which is causing the problem and executed the following command:
dbcc checktable('inbox',REPAIR_ALLOW_DATA_LOSS).
The output was. CHECKTABLE fixed 0 allocation errors and 90 consistency errors in table 'inbox'
after that i made the db to single user and executed dbcc checkdb and the output was
CHECKDB found 0 allocation errors and 88 consistency errors in database 'HelloDB'.
Server: Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 37575172, index ID 0, page (1:96043). Test (IS_ON (BUF_IOERR, bp->bstat) && bp-
>berrcode) failed. Values are 2057 and -1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 37575172, index ID 0, page (1:96045). Test (IS_ON (BUF_IOERR, bp->bstat) && bp-
>berrcode) failed. Values are 2057 and -1.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'HelloDB', index 'Inbox.PK_Inbox' (ID 37575172) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:152032:187) with values (MessageID =3D C9C9BD2B-
C135-487C-B26E-006FDB45B523d=A2=EE ) points to the data row identified by (RID =3D (1:96045:20)).
.
.
.
.
I am confused why it is showing inconsistency errors for DBCC Checkdb whereas it showed all the errors are fixed when checktable was run.
The improvement I found was, even it shows errors on DBCC CheckDB, it is not affecting the Operatins on DB.( before dbcc checktable the db was non operational)
Can anyone suggest on what is happening? and how to overcome this situation?
Hoping for a Quick reply
Thanks in Advance
Regards
ThirumalHi All,
At last I could find the soultion. KB says that Error:Server: Msg 8939, Level 16, State 98, Line 1
CAUSE
The sysindexes.status field should have a value of 2097152 so that the nonclustered index column can allow the insertion of NULL values for both SQL Server 7.0 and SQL Server 2000.
In SQL Server 7.0, if the sysindexes.status value is 0 for the nonclustered index in a table, the nonclustered index also allows the insertion of NULL values. If you run a DBCC CHECKDB statement on the SQL Server 7.0 database, the problem is not reported. After you upgrade the table in SQL Server 2000, the DBCC CHECKDB statement reports the error message described in the "Symptoms" section because a NULL value is not allowed when the sysindexes.status value is not 2097152.
I have run the DBCC DBREINDEX as
DBCC DBREINDEX ('inbox','',0)
after this i have run
dbcc checkdb
no errors Reported
I request the experts to suggest what I have done is proper or not?
Regards
Thirumal
>--Original Message--
>Hi All,
>I had a database tornpage detected and at traced the table >which is causing the problem and executed the following >command:
>dbcc checktable('inbox',REPAIR_ALLOW_DATA_LOSS).
>The output was. CHECKTABLE fixed 0 allocation errors and >90 consistency errors in table 'inbox'
>after that i made the db to single user and executed dbcc >checkdb and the output was >CHECKDB found 0 allocation errors and 88 consistency >errors in database 'HelloDB'. >Server: Msg 8939, Level 16, State 98, Line 1
>Table error: Object ID 37575172, index ID 0, page >(1:96043). Test (IS_ON (BUF_IOERR, bp->bstat) && bp-
>>berrcode) failed. Values are 2057 and -1.
>Server: Msg 8939, Level 16, State 1, Line 1
>Table error: Object ID 37575172, index ID 0, page >(1:96045). Test (IS_ON (BUF_IOERR, bp->bstat) && bp-
>>berrcode) failed. Values are 2057 and -1.
>Server: Msg 8952, Level 16, State 1, Line 1
>Table error: Database 'HelloDB', index 'Inbox.PK_Inbox' >(ID 37575172) (index ID 2). Extra or invalid key for the >keys:
>Server: Msg 8956, Level 16, State 1, Line 1
>Index row (1:152032:187) with values (MessageID =3D C9C9BD2B-
>C135-487C-B26E-006FDB45B523d=A2=EE ) points to the data row >identified by (RID =3D (1:96045:20)).
>..
>..
>..
>..
>I am confused why it is showing inconsistency errors for >DBCC Checkdb whereas it showed all the errors are fixed >when checktable was run.
>The improvement I found was, even it shows errors on DBCC >CheckDB, it is not affecting the Operatins on DB.( before >dbcc checktable the db was non operational)
>Can anyone suggest on what is happening? and how to >overcome this situation?
>Hoping for a Quick reply
>Thanks in Advance
>Regards
>Thirumal
>.
>