Post reply

SQL Server Database - IAM Page errors

  • January 16, 2003 at 1:01 pm

    #58752

    Hi,

    I am getting the following errors in Integrity jobs. Could I get some help to fix this errors.

    [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:171) object ID 501576825 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 (1:1834) object ID 1792217635 index ID 0 but was not detected in the scan.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Chain sequence numbers are out of order in IAM chain for object ID 1792217635, index ID 0. Page (1:417243) sequence number 1 points to page (1:2466) sequence number 0.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Chain sequence numbers are out of order in IAM chain for object ID 1792217635, index ID 0. Page (1:1834) sequence number 1 points to page (1:417243) sequence number 0.

    [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:453166) object ID 1792217635 index ID 2 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 (1:453167) object ID 1792217635 index ID 3 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 (1:455560) object ID 1792217635 index ID 4 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 (1:455561) object ID 1792217635 index ID 5 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 (1:455563) object ID 1792217635 index ID 6 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 (1:455564) object ID 1792217635 index ID 7 but was not detected in the scan.

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

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

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

    I did CHECKDB, CHECKALLOC and everything and it didn't seem working.

    Need help Please,

    Thank you,

    Rearasi

  • January 16, 2003 at 2:37 pm

    #446561

    You ran CHECKDB with the REPAIR_ALLOW_DATA_LOSS option and it didn't fix it? You have to specify this option explicitly.

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • January 16, 2003 at 5:10 pm

    #446584

    Just as important, Have you determined what corrupted your database like that so that you can prevent it from happening again?

    After all, According to the instructors I've attended class with and Microsoft, It's no longer neccessary to DBCC your databases ....LMAO

    Yall better believe I know better....I bet rearasi does too.....

  • January 17, 2003 at 7:44 am

    #446623

    The instructors I believe, but the folks on the DB side I've worked with at MS believe in DBCC CHECKDB on a regular basis (consider that it can be scheduled as part of a maintenance plan).

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • January 17, 2003 at 11:36 am

    #446673

    Yes, I ran CHECKDB with the REPAIR_ALLOW_DATA_LOSS option explicitly. It didn't fix the problem. I am still getting the same errors. I don't know what else I can go with. This seems very strange to me.

    Thanks,

    Rearasi

  • January 17, 2003 at 11:38 am

    #446675

    How recent was your last backup?

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

Viewing 6 posts - 1 through 5 (of 5 total)

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