Integrity check error

  • I get this strange error meassge when doing an integrity check on one of my databases. The ids that the error message  produce doesnt seem to be existing in sysobjects because of which its difficult to find out where the problem is. can anyone please shed some light why its happening. Heres the error that i see in my log file.

    TIA

     

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 2576: [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (3:3695) object ID 661577395 index ID 0 but was not detected in the scan.              

    (null)

        The following errors were found:                                                                                                                                                                                                                          

    (null)

    [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (3:3695) object ID 661577395 index ID 0 but was not detected in the scan.

                                                                        

    [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (4:14) object ID 1413580074 index ID 8 but was not detected in the scan.

                                                                         

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 2 allocation errors and 0 consistency errors in table '(Object ID 1461580245)' (object ID 1461580245).                                                                                           

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 28 allocation errors and 0 consistency errors in database 'XXXX'.                                                                                                      

    [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (XXXX ).                                                                                     

    (null)

        ** Execution Time: 0 hrs, 4 mins, 2 secs **                                                                                                       

  • This was removed by the editor as SPAM

  • First thing, try recreating the indexes on that table (drop and create, or create with drop existing) and see if that resolves the problem.



    Shamless self promotion - read my blog http://sirsql.net

  • if that doesnt work you will have to do a dbcc checkdb repair with allow data loss to fix it. You may want to DTS the data out of the tables that have errors if you can then compair them to the rebuilt ones after the repair job to see if you have lost any data.

    Wes

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

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