Post reply

Database Consistency problems

  • September 23, 2003 at 10:10 am

    #65110

    Yesterday one of our sql 2K server (Win 2k) raised a red flag. (See below)

    1). What is a "consistency" error, mentioned below? Are they referring to RI?

    2. Regarding the errors shown below

    I don't know what they mean, what caused them, how to correct them, or how to prevent them in the future. Any advice appreciated (of course, the goal is a solid DB but achieved with minimum data loss).

    TIA,

    Bill

    >>>>>>>

    [7] Database myiCA: Check Data and Index Linkage...

    ** Execution Time: 0 hrs, 0 mins, 5 secs **

    Database myiCATemp: Check Data and Index Linkage...

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 1117247035,

    index ID 0: Page (1:2183) could not be processed. See other errors for details.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1117247035, index ID 0, page (1:2183), row 16.

    Test (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values are 350 and 348.

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors

    in table 'mytblPO' (object ID 1117247035).

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in

    database 'myiCATemp'.

    [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors

    found by DBCC CHECKDB (myiCATemp ).

    ** Execution Time: 0 hrs, 0 mins, 14 secs **

    >>>>>>>

  • September 23, 2003 at 10:35 am

    #475459

    I suspect that some of the pointers are potentially out of whack. Can you drop and rebuild this index and then try to run the dbcc. That has worked in correcting minor errors for me.

    Steve Jones

    sjones@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/sjones

    The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/

    http://www.dkranch.net

  • September 25, 2003 at 2:17 pm

    #475876

    Steve is absolutely correct. We had an index inter-leaved with another index. We dropped and rebuilt both and everything has been fine since. Be sure to rebuild the offending indexes (or all for the tables, if you not sure which is corrupted).

    Terry


    Terry

  • September 25, 2003 at 7:31 pm

    #475908

    You advice is good!

    Despite the ominous error message I received when I re-ran our Integrity job those databases came out smelling like a rose!

    Thanks.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply