/build/static/layout/Breadcrumb_cap_w.png

Damage of the SQL database

Good day, friends!

There is the following situation.  On one server, I make a backup of the database. With integrity check everything is carried out. Transfer the backup to another server and restore from it base, has also successfully completed. I do a couple of selects from the tables just in case, selects are work. After that didn't touch base. Suddenly after a few hours started pouring in an error like

Table error: alloc unit ID 72057606917455872, page (1:1163817) contains an incorrect page ID in its page header. The PageId in the page header = (1:8696745).

Doing DBCC CHECKDB but it fails.

[color=red]Msg 7985, Level 16, State 2, Line 1

System table pre-checks: Object ID 3. Could not read and latch page (1:1163817) with latch type SH. Check statement terminated due to unrepairable error.[/color]

DBCC results for 'DWH_Globus'.

[color=red]Msg 5256, Level 16, State 1, Line 1

Table error: alloc unit ID 72057606917455872, page (1:1163817) contains an incorrect page ID in its page header. The PageId in the page header = (1:8696745).[/color]

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

CHECKDB found 0 allocation errors and 1 consistency errors in database 'DWH_Globus'.

ObjectId 3 - system table. I don't know how it could be damaged. To SAN there were no errors. In Event Viewer there are no errors, except these.

ОС - WinServer 2012 R2, SQL Server 2012 SP2 CU4 EE. 

Except me nobody touched base.  Prompt, please, because of what such can happen not to run on the same mistakes next time.  


0 Comments   [ + ] Show comments

Answers (0)

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ