DBCC CheckDB errors - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

DBCC CheckDB errors

Author

Topic

bjattolico
Starting Member

2 Posts

Posted - 2015-03-30 : 13:42:27

Hello

System is SQL server 2012 SP2 version 11.0.5058

Ran DBCC CHECKDB ([VCDB]) WITH No_INFOMSGS, ALL_ERRORMSGS on database with this result:

Incorrect PFS free space information for page (1:62425) in object ID 389576426, index ID 1, partition ID 72057594040090624, alloc unit ID 72057594044350464 (type LOB data). Expected value 50_PCT_FULL, actual value 0_PCT_FULL.
Msg 2533, Level 16, State 1, Line 2
Table error: page (1:62425) allocated to object ID 389576426, index ID 1, partition ID 72057594040090624, alloc unit ID 72057594044284928 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2534, Level 16, State 2, Line 2
Table error: page (1:62425), whose header indicates that it is allocated to object ID 389576426, index ID 1, partition ID 72057594040090624, alloc unit ID 72057594044350464 (type LOB data), is allocated by another object.
Msg 8980, Level 16, State 1, Line 2
Table error: Object ID 389576426, index ID 1, partition ID 72057594040090624, alloc unit ID 72057594044284928 (type In-row data). Index node page (1:67613), slot 195 refers to child page (1:62425) and previous child (1:62424), but they were not encountered.
Msg 8964, Level 16, State 1, Line 2
Table error: Object ID 389576426, index ID 1, partition ID 72057594040090624, alloc unit ID 72057594044350464 (type LOB data). The off-row data node at page (1:62425), slot 52, text ID 390790512640 is not referenced.
Msg 8978, Level 16, State 1, Line 2
Table error: Object ID 389576426, index ID 1, partition ID 72057594040090624, alloc unit ID 72057594044284928 (type In-row data). Page (1:62426) is missing a reference from previous page (1:62425). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'VPX_EVENT_ARG' (object ID 389576426).
CHECKDB found 0 allocation errors and 6 consistency errors in database 'VCDB'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (VCDB).

There is a full backup that from 3/21 and differential backups after that. The database will backup now.

How should I proceed?

Thank you very much for your help

bjattolico
Starting Member

2 Posts

Posted - 2015-03-30 : 17:26:19

After reading other articles we explored our backups and when the corruption took place. The application for this database crashed on that day. There was corruption in a non critical table only so we corrected it with this DBCC CHECKDB (VCDB, REPAIR_ALLOW_DATA_LOSS) with all_errorMSGS .

Lincolnburrows
Yak Posting Veteran

52 Posts

Posted - 2015-05-27 : 05:26:08

Get restore from full backup of the SQL database

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources