SQL Server Performance Forum – Threads Archive

Corrupt Database

I had a raid failure on a SQL 200 SP4 server and i have a database that states it is corrupt. I am very new to SQL and would like to know if there is a way to repair the database with out losing data. The only non corrupt backup i have is 7 days old so i am unable to revert to it. I ran DBCC CHKDB and got the below results. Any advise would be greatly appreciated. DBCC results for ‘KShipU’. DBCC results for ‘sysobjects’. There are 98 rows in 2 pages for object ‘sysobjects’. DBCC results for ‘sysindexes’. There are 211 rows in 10 pages for object ‘sysindexes’. DBCC results for ‘syscolumns’. There are 657 rows in 14 pages for object ‘syscolumns’. DBCC results for ‘systypes’. There are 26 rows in 1 pages for object ‘systypes’. DBCC results for ‘syscomments’. There are 131 rows in 16 pages for object ‘syscomments’. DBCC results for ‘sysfiles1’. There are 2 rows in 1 pages for object ‘sysfiles1’. DBCC results for ‘syspermissions’. There are 49 rows in 1 pages for object ‘syspermissions’. DBCC results for ‘sysusers’. There are 14 rows in 1 pages for object ‘sysusers’. DBCC results for ‘sysproperties’. There are 0 rows in 0 pages for object ‘sysproperties’. DBCC results for ‘sysdepends’. There are 474 rows in 3 pages for object ‘sysdepends’. DBCC results for ‘sysreferences’. There are 0 rows in 1 pages for object ‘sysreferences’. DBCC results for ‘sysfulltextcatalogs’. There are 0 rows in 1 pages for object ‘sysfulltextcatalogs’. DBCC results for ‘sysfulltextnotify’. There are 0 rows in 0 pages for object ‘sysfulltextnotify’. DBCC results for ‘sysfilegroups’. There are 1 rows in 1 pages for object ‘sysfilegroups’. DBCC results for ‘Addresses’. There are 2551 rows in 59 pages for object ‘Addresses’. DBCC results for ‘AddressGroups’. There are 0 rows in 1 pages for object ‘AddressGroups’. DBCC results for ‘AddressGroups_Addresses’. There are 0 rows in 1 pages for object ‘AddressGroups_Addresses’. DBCC results for ‘Commodities’. There are 5 rows in 2 pages for object ‘Commodities’. DBCC results for ‘ContentOptions’. There are 561205 rows in 5471 pages for object ‘ContentOptions’. DBCC results for ‘Departments’. There are 1 rows in 1 pages for object ‘Departments’. DBCC results for ‘Dimensions’. There are 0 rows in 1 pages for object ‘Dimensions’. DBCC results for ‘DupeCheck’. There are 0 rows in 1 pages for object ‘DupeCheck’. DBCC results for ‘PackageOptions’. There are 505571 rows in 3539 pages for object ‘PackageOptions’. DBCC results for ‘Preferences’. There are 176 rows in 4 pages for object ‘Preferences’. DBCC results for ‘ShipmentOptions’. There are 893191 rows in 5598 pages for object ‘ShipmentOptions’. DBCC results for ‘StateZip’. There are 0 rows in 1 pages for object ‘StateZip’. DBCC results for ‘ManSendLog’. There are 8505 rows in 144 pages for object ‘ManSendLog’. DBCC results for ‘ShipmentCounter’. There are 0 rows in 8 pages for object ‘ShipmentCounter’. DBCC results for ‘ObjectProperties’. There are 273 rows in 4 pages for object ‘ObjectProperties’. DBCC results for ‘ShipAddresses’. There are 0 rows in 1 pages for object ‘ShipAddresses’. DBCC results for ‘IntlInfo’. There are 57 rows in 2 pages for object ‘IntlInfo’. DBCC results for ‘dtproperties’. There are 0 rows in 1 pages for object ‘dtproperties’. DBCC results for ‘Packages’. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1397580017, index ID 0: Page (1:7016) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1397580017, index ID 0, page (1:7016), row 1. Test (ColumnOffsets <= (nextRec – pRec)) failed. Values are 16336 and 219. Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 1397580017, index ID 0, page ID (1:7017). The PageId in the page header = (1:7021). Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1397580017, index ID 0: Page (1:7017) could not be processed. See other errors for details. Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 1397580017, index ID 0, page ID (1:701<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ />. The PageId in the page header = (1:7022). Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1397580017, index ID 0: Page (1:701<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ /> could not be processed. See other errors for details. Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 1397580017, index ID 0, page ID (1:7019). The PageId in the page header = (1:7023). Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1397580017, index ID 0: Page (1:7019) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1397580017, index ID 0: Page (1:7020) could not be processed. See other errors for details. Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 1414549324, index ID 12848, page ID (1:7020). The PageId in the page header = (52672:1703984). There are 778187 rows in 22412 pages for object ‘Packages’. CHECKDB found 0 allocation errors and 9 consistency errors in table ‘Packages’ (object ID 1397580017). CHECKDB found 0 allocation errors and 1 consistency errors in table ‘(Object ID 1414549324)’ (object ID 1414549324). DBCC results for ‘Shipments’. There are 733773 rows in 73036 pages for object ‘Shipments’. DBCC results for ‘PackageHazmat’. There are 0 rows in 1 pages for object ‘PackageHazmat’. DBCC results for ‘ArchiveLog’. There are 0 rows in 0 pages for object ‘ArchiveLog’. CHECKDB found 0 allocation errors and 10 consistency errors in database ‘KShipU’. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (KShipU ). DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Run this command to see if you can repair any minor errors DBCC CHECKDB (‘KShipU’, REPAIR_FAST) this will not expose you to data loss. Raulie

I will try this tonight and post the results again. Thanks for you quick response

99% of the times repair_fast will not work… First thing if you can get the data out copy the data to a new table…
Then take the row count and run the repair with repair_allow_data_loss option… If table not repaired with repair_allow_data_loss option and you were able to take out the data to a new table then drop the existing table and rename the new table…
MohammedU.
Microsoft SQL Server MVP
Moderator
SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy.

There was a good disucussion by Paul Randal inhttp://www.sqlteam.com/forums/topic.asp?TOPIC_ID=64564&http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=58529 links. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

]]>