Recurring Inconsistency on SQL2000 running on Win2003.
-
I'm at my wits end.... please help.
I have posted a similar entry before, a few hardware upgrades were done on the server in question in the meantime (not to sure exactlying, seeing that we are not responsible for the server administration... think it was regarding hyperthreading and BIOS levels), but the problem is still occurring (4 times on the same instance, and same db already... and, it never used to occur on the previous server from which these db's migrated). We are running 5 instances of SQL Server2000 SP3(8.00.760) on a consolidated server (8 physical processors, 8 virtual processors) in a SAN. MDAC version 2.8, Emulex 9002 cards (I think), and FastT900 disks.
As precaution, TornPageDetection is switched on on all the db's, and we are running integrity checks on the db's every evening, and last night it fell over for inconsistency errors again. The following message was written to a text file by die Integrity Check job:
[4] Database Genome: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 309576141, index ID 12: Page (1:89638) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 309576141, index ID 12, page (1:89638), row 166. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 3748 and 24.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in table 'LinkThree' (object ID 309576141).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in database 'Genome'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Genome ).The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 309576141, index ID 12: Page (1:89638) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 309576141, index ID 12, page (1:89638), row 166. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 3748 and 24.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in table 'LinkThree' (object ID 309576141).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in database 'Genome'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Genome ).
** Execution Time: 0 hrs, 1 mins, 26 secs **Repairing the problem is not my issue, but solving it, that is. Any suggestions???
Thanks.
-
If it's a recurring inconsistency on the same table (LinkThree) and index (id 12)then I'd say you do have an inconsistency problem but the good news is that - because it's not the clustered index - you can fix it just by dropping that index and recreating it.
If it's a recurring inconsistency on different tables each time, and say LinkThree doesn't always show up, then my guess it's one of the transient DBCC errors that are thrown up because of concurrent activity on the database - a backup, reorg, updatestats, or even oltp activity.
I've seen transient errors when a DBA (not necessarily me
) has stupidly scheduled reorgs to happen across the db backup window.Try restoring the database as another temporary database and DBCC'ing it.
Cheers,
- Mark -
Hello:
I encountered the same problem. Have anyone tried to deleted and re-created the index? Possible something to do with the hardware?
Our situation is that we have a new SCSI disk, I moved the data file from the old SCSI disk to the new SCSI disk. Then I did a integrity check and there came the error! I did an integrity check two weeks ago, and the database was fine!
Thanks,
Joe
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply