none
Massive sql dump files happening. RRS feed

  • Question

  • Last night all of a sudden the C: drive on the Windows2016 server maxed out by sql creating multiple sql dump files. 

    I looked into the .txt file and .log but I am a little lost. As a result I ran the following command DBCC CHECKDB with one of the databases that caused this issue. I have pasted below the issues of the matter below. I do not know what to do at this point other than peforming Repair_allow_data_loss. Could you guys please shed some light on this matter. 

    Please note after deleting the files last night, there hasn't been any new sql dump files created in the last 24 hours. So I am not sure what happened for this to trigger.

    Msg 2511, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). Keys out of order on page (4:599629), slots 61 and 62.
    Msg 8944, Level 16, State 13, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data), page (4:621622), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 393 and 50.
    Msg 8937, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). B-tree page (4:3888) has two parent nodes (4:172), slot 0 and (4:4056), slot 0.
    Msg 8934, Level 16, State 2, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). The high key value on page (4:3879) (level 0) is not less than the low key value in the parent (4:172), slot 0 of the next page (4:3888).
    Msg 8934, Level 16, State 3, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). The high key value on page (4:3879) (level 0) is not less than the low key value in the parent (4:172), slot 0 of the next page (4:3888).
    Msg 8937, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). B-tree page (4:5156) has two parent nodes (4:5354), slot 1 and (4:628449), slot 0.
    Msg 8937, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). B-tree page (4:44049) has two parent nodes (4:98815), slot 58 and (4:628449), slot 49.
    Msg 8935, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). The previous link (4:884939) on page (4:46434) does not match the previous page (4:580347) that the parent (4:599629), slot 57 expects for this page.
    Msg 8937, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). B-tree page (4:46434) has two parent nodes (0:1), slot 0 and (4:98815), slot 60.
    Msg 8981, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). The next pointer of (4:742792) refers to page (4:156658). Neither (4:156658) nor its parent were encountered. Possible bad chain linkage.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). Page (4:205928) is missing a reference from previous page (4:657090). Possible chain linkage problem.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). Page (4:205976) is missing a reference from previous page (4:742794). Possible chain linkage problem.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). Page (4:206056) is missing a reference from previous page (4:657094). Possible chain linkage problem.
    Msg 8925, Level 16, State 1, Line 1
    Table error: Cross object linkage: Page (4:628449), slot 1, in object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data), refers to page (4:222267), slot 0, in object ID 629577281, index ID 1, partition ID 72057594039042048, alloc unit ID 72057594043432960 (type In-row data).
    Msg 8937, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 1, partition ID 72057594039042048, alloc unit ID 72057594043432960 (type In-row data). B-tree page (4:222267) has two parent nodes (0:1), slot 0 and (4:222541), slot 85.
    Msg 8937, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). B-tree page (4:237221) has two parent nodes (4:240861), slot 77 and (4:628449), slot 50.
    Msg 8937, Level 16, State 1, Line 1
    Table error: Object ID 629577281, index ID 4, partition ID 72057594133938176, alloc unit ID 72057594160545792 (type In-row data). B-tree page (4:249107) has two parent nodes (4:281890), slot 23 and (4:599629), slot 60.
    Msg 8936, Level 16, State 1, Line 1

    Wednesday, September 11, 2019 8:21 PM

All replies