Post reply

Unable to read and latch page

  • August 9, 2016 at 4:29 pm

    #328859

    Hi there,

    Our database cannot be backup up and we are getting the below error. We found out that the corrupt is under a table with data with no importance to lose. What do you suggest? truncate the table will fix the issue? please let us know your opinion.

    Hi,

    Our database cannot be backup up and we are getting the below error. We found out that the corrupt is under a table with data with no importance to lose. What do you suggest? truncate the table will fix the issue? please let us know your opinion.

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    Msg 8966, Level 16, State 2, Line 3

    Unable to read and latch page (1:5609991) with latch type SH. 23(failed to retrieve text for this error. Reason: 15105) failed.

    Msg 2514, Level 16, State 1, Line 3

    A DBCC PAGE error has occurred: page not found.

    Thanks in advance

    Thanks

  • August 9, 2016 at 4:35 pm

    #1894675

    Please run the following and post the full output

    DBCC CheckDB('<database name>') WITH NO_INFOMSGS, ALL_ERRORMSGS

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 9, 2016 at 4:58 pm

    #1894679

    Thanks for the fast reply.

    Here is the results. Please have in mind that we had a bad sector on a RAID disk which we replaced but the problem still persists.

    Msg 8966, Level 16, State 2, Line 1

    Unable to read and latch page (1:5609991) with latch type SH. 23(failed to retrieve text for this error. Reason: 15105) failed.

    CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:5609991) allocated to object ID 871674153, index ID 2, partition ID 72057594197245952,

    alloc unit ID 72057594226606080 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 8976, Level 16, State 1, Line 1

    Table error: Object ID 871674153, index ID 2, partition ID 72057594197245952, alloc unit ID 72057594226606080 (type In-row data).

    Page (1:5609991) was not seen in the scan although its parent (1:7447585) and previous (1:6032874) refer to it. Check any previous errors.

    Msg 8978, Level 16, State 1, Line 1

    Table error: Object ID 871674153, index ID 2, partition ID 72057594197245952, alloc unit ID 72057594226606080 (type In-row data).

    Page (1:5845499) is missing a reference from previous page (1:5609991). Possible chain linkage problem.

    CHECKDB found 0 allocation errors and 3 consistency errors in table 'table_xxxx' (object ID 871674153).

    CHECKDB found 0 allocation errors and 4 consistency errors in database 'database_xxxx'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB ('database_xxxx'.).

    Msg 8966, Level 16, State 2, Line 1

    Unable to read and latch page (1:5609991) with latch type SH. 23(failed to retrieve text for this error. Reason: 15105) failed.

    Msg 2514, Level 16, State 1, Line 1

    A DBCC PAGE error has occurred: page not found.

  • August 10, 2016 at 1:42 am

    #1894721

    If you're absolutely certain that table_xxxx has no important data, then you can run CheckDB with the repair_allow_data_loss option and it will fix the damage.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 10, 2016 at 1:54 am

    #1894722

    Thanks again!

    If we run DBCC CHECKTABLE with REPAIR_ALLOW_DATA_LOSS is it going to minimize the risk? it will do the same job? also TRUNCATE the table will not work right?

    thanks a lot for your valuable time. hope this to help others also.

  • August 10, 2016 at 2:01 am

    #1894723

    You can try that, but I'm not sure it'll fix everything.

    Unable to read and latch page (1:5609991) with latch type SH. 23(failed to retrieve text for this error. Reason: 15105) failed.

    CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

    It might, it might not. I'm not sure.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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