August 1, 2014 at 4:47 pm
When checkdb completes without error, then I'd say you have plenty of proof to show them that the storage is not ok.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 2, 2014 at 4:47 am
I ran the CHECK INTEGRITY on the db on the other SQL Server and there IS corruption.... so much that I didn't cut/paste it all into this thread.....
Msg 8929, Level 16, State 1, Line 1
Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046251008 (type In-row data): Errors found in off-row data with ID 195654194757632 owned by data record identified by RID = (1:25506:7)
Msg 8929, Level 16, State 1, Line 1
Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046251008 (type In-row data): Errors found in off-row data with ID 189244556705792 owned by data record identified by RID = (1:25995:2)
Msg 8929, Level 16, State 1, Line 1
Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046251008 (type In-row data): Errors found in off-row data with ID 68361383968768 owned by data record identified by RID = (1:41810:5)
Msg 8929, Level 16, State 1, Line 1
Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046251008 (type In-row data): Errors found in off-row data with ID 178353223172096 owned by data record identified by RID = (1:59328:3)
Msg 8929, Level 16, State 1, Line 1
Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046251008 (type In-row data): Errors found in off-row data with ID 160533692284928 owned by data record identified by RID = (1:71634:0)
Msg 8929, Level 16, State 1, Line 1
Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046251008 (type In-row data): Errors found in off-row data with ID 165566600314880 owned by data record identified by RID = (1:86261:12)
Msg 8929, Level 16, State 1, Line 1
Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046251008 (type In-row data): Errors found in off-row data with ID 139702217539584 owned by data record identified by RID = (1:88819:1)
Msg 8929, Level 16, State 1, Line 1
Table error: Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046316544 (type LOB data). The off-row data node at page (1:77771107), slot 0, text ID 118088654127104 does not match its reference from page (1:6118388), slot 0.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046316544 (type LOB data). The off-row data node at page (1:77771108), slot 0, text ID 118088654127104 does not match its reference from page (1:6118388), slot 0.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046316544 (type LOB data). The off-row data node at page (1:77771109), slot 0, text ID 118088654127104 does not match its reference from page (1:6118388), slot 0.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046316544 (type LOB data). The off-row data node at page (1:77771286), slot 0, text ID 118088654127104 does not match its reference from page (1:6118388), slot 0.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 162099618, index ID 0, partition ID 72057594040942592, alloc unit ID 72057594046316544 (type LOB data). The off-row data node at page (1:77972514), slot 0, text ID 125279715393536 does not match its reference from page (1:29651279), slot 0.
CHECKDB found 0 allocation errors and 41303 consistency errors in table 'CntItmPrgs' (object ID 162099618).
CHECKDB found 0 allocation errors and 41303 consistency errors in database 'DBTEST3'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DBTEST3).
August 5, 2014 at 11:04 am
I am now having the storage team look into the IO and back end storage. There has to be an issue somewhere in one of the layers.
August 5, 2014 at 11:06 am
Markus (8/5/2014)
I am now having the storage team look into the IO and back end storage. There has to be an issue somewhere in one of the layers.
I'd agree with that.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 4 posts - 46 through 48 (of 48 total)
You must be logged in to reply to this topic. Login to reply