DBCC - Possible chain linkage problem

[JamesJKusch]

Ran DBCC CHECKDB and had a couple of issues. need to know if in exporting/backuping up the table(s), Dropping and then Recreate the table(s) and then reload data will correct the problem OR is there no other way around the issue besides using the "REPAIR_ALLOW_DATA_LOSS" option.

==========================================================
Here is the DBCC report:
==========================================================
DBCC results for 'MARKETING_COUNTER'.
There are 199879 rows in 4242 pages for object 'MARKETING_COUNTER'.
Server: Msg 8939, Level 16, State 7, Line 0
Table Corrupt: Object ID 816721962, index ID 0, page (1:2143820). Test (m_freeData >= PAGEHEADSIZE && m_freeData <= PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values are 38626 and 8164. Server: Msg 8928, Level 16, State 1, Line 0
Object ID 816721962, index ID 1: Page (1:2143820) could not be processed. See other errors for details. Server: Msg 8976, Level 16, State 1, Line 0 Table Corrupt: Object ID 816721962, index ID 1. Page (1:2143820) not allocated or corrupt. Parent (1:2230016) and previous (1:2143819) refer to it. Server: Msg 8978, Level 16, State 1, Line 0
Table Corrupt: Object ID 816721962, index ID 1. Page (1:2143821) is missing a reference from previous page (1:2143820). Possible chain linkage problem

==========================================================
At the end of the report DBCC gives the following advise:
==========================================================

CHECKDB found 0 allocation errors and 13 consistency errors in database 'Reports'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Reports ). DBCC execution completed. If DBCC printed error messages, contact your system administrator.

==========================================================
This is the description of what &quot;REPAIR_ALLOW_DATA_LOSS&quot;
option does and the issue of &quot;POSSIBLE DATA LOSS&quot; i am trying to avoid if possible
==========================================================

REPAIR_ALLOW_DATA_LOSS

Performs all repairs done by REPAIR_REBUILD and includes allocation and deallocation of rows and pages for
correcting allocation errors, structural row or page errors, and deletion of corrupted text objects. These repairs can result in some data loss. The repair may be done under a user transaction to allow the user to roll back the changes made. If repairs are rolled back, the database will still contain errors and should be restored from a backup. If a repair for an error has been skipped due to the provided repair level, any repairs that depend on the repair are also skipped. After repairs are completed, back up the database.



Thanks for all the help ... As Usual

J. Kusch
Chameleon Solutions, Inc.

 

[foxdev]

need to know if in exporting/backuping up the table(s), Dropping and then Recreate the table(s) and then reload data will correct the problem

My guess is that the success of this approach depends on if you can get the data accurately exported. IOW, if there is a problem with a table, and you run an export (DTS or BCP), would the correct data and all the data get successfully exported?

In any event, I'd make some text-format exports first before you do anything, regardless of which approach you take. Robert Bradley

http://www.lowcostprints.com

http://www.foxdev.com/

http://www.agrainofhope.org

 

[JamesJKusch]

Right on the money w/ those statements. have been testing w/ bcp and it &quot;seems&quot; like the export is valid. going to bring it back into a test table on our developemt sys to see if there are any hiccups in that process. thanks for the info and pointers.

J. Kusch Thanks for all the help ... As Usual

J. Kusch
Chameleon Solutions, Inc.