DBCC checkdb report error

  • Gurus,

    When I performed DBCC checkdb on my this database it reports following error. Any help.

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16392). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16393). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16394). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16395). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16396). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16397). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16398). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16399). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16416). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16417). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16418). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16419). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16420). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16421). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16422). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16423). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16440). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16441). The PageId in the

    page header = (0:0). DBCC results for 'db_work'.

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16442). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16443). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16444). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16445). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16446). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16447). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16464). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16465). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16466). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16467). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:16468). The PageId in the

    page header = (0:0).

    Server: Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID 0, page ID (1:20016). The PageId in the

    page header = (0:0).

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16392) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16393) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16394) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16395) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16396) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16397) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16398) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16399) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16416) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16417) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16418) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16419) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16420) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16421) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16422) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16423) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16440) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16441) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16442) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16443) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16444) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16445) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16446) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16447) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16464) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16465) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16466) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16467) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:16468) could not be processed. See

    other errors for details.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 885578193, index ID 0: Page (1:20016) could not be processed. See

    other errors for details. CHECKDB found 0 allocation errors and 30

    consistency errors not associated with any single object. DBCC results for

    'sysobjects'. There are 162 rows in 3 pages for object 'sysobjects'. DBCC

    results for 'sysindexes'. There are 121 rows in 7 pages for object

    'sysindexes'. DBCC results for 'syscolumns'. There are 746 rows in 15 pages

    for object 'syscolumns'. DBCC results for 'systypes'. There are 26 rows in 1

    pages for object 'systypes'. DBCC results for 'syscomments'. There are 212

    rows in 28 pages for object 'syscomments'. DBCC results for 'sysfiles1'.

    There are 4 rows in 1 pages for object 'sysfiles1'. DBCC results for

    'syspermissions'. There are 82 rows in 1 pages for object 'syspermissions'.

    DBCC results for 'sysusers'. There are 21 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 930

    rows in 4 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 'tbl_Loss_Prior_Day_Backup'. There are 27712 rows in 1260

    pages for object 'tbl_Loss_Prior_Day_Backup'. DBCC results for

    'dtproperties'. There are 0 rows in 1 pages for object 'dtproperties'. DBCC

    results for 'tbl_wandinfo'. There are 0 rows in 1 pages for object

    'tbl_wandinfo'. DBCC results for 'tbl_admitted_975'. There are 42138 rows in

    543 pages for object 'tbl_admitted_975'. DBCC results for 'tbl_pcoverage'.

    There are 656824 rows in 5121 pages for object 'tbl_pcoverage'. DBCC results

    for 'tbl_log_application_run'. There are 446 rows in 16 pages for object

    'tbl_log_application_run'. DBCC results for 'tbl_pcommon_mgmt'. There are

    272853 rows in 1681 pages for object 'tbl_pcommon_mgmt'. DBCC results for

    'tbl_pcommon'. There are 314054 rows in 3784 pages for object 'tbl_pcommon'.

    DBCC results for 'tbl_Loss_Curr_Day'. There are 175 rows in 8 pages for

    object 'tbl_Loss_Curr_Day'. DBCC results for 'tbl_lc87_name_d'. There are

    410951 rows in 2834 pages for object 'tbl_lc87_name_d'. DBCC results for

    'tbl_lc87_agent_d'. There are 702 rows in 10 pages for object

    'tbl_lc87_agent_d'. DBCC results for 'CRESERVE'. There are 12079 rows in 806

    pages for object 'CRESERVE'. DBCC results for 'tbl_TaxReport'. There are

    47458 rows in 4746 pages for object 'tbl_TaxReport'. DBCC results for

    'tbl_pforms'. There are 1831178 rows in 9944 pages for object 'tbl_pforms'.

    CHECKDB found 0 allocation errors and 30 consistency errors in table

    'tbl_pforms' (object ID 885578193). DBCC results for 'tbl_extract_limits'.

    There are 997 rows in 29 pages for object 'tbl_extract_limits'. DBCC results

    for 'tbl_Loss_Prior_Day'. There are 27750 rows in 1207 pages for object

    'tbl_Loss_Prior_Day'. DBCC results for 'tbl_Loss_Prior_Mth'. There are 27750

    rows in 1207 pages for object 'tbl_Loss_Prior_Mth'. DBCC results for

    'tbl_log_month_end_run'. There are 27 rows in 1 pages for object

    'tbl_log_month_end_run'. DBCC results for 'tbl_ME_SP_Master_List'. There are

    27 rows in 1 pages for object 'tbl_ME_SP_Master_List'. DBCC results for

    'tbl_Extract_NursingHome'. There are 21 rows in 1 pages for object

    'tbl_Extract_NursingHome'. CHECKDB found 0 allocation errors and 60

    consistency errors in database 'db_work'. repair_allow_data_loss is the

    minimum repair level for the errors found by DBCC CHECKDB (db_work ). DBCC

    execution completed. If DBCC printed error messages, contact your system

    administrator.

  • If you didn't do it, run again the DBCC CHECKDB command with the REPAIR_ALLOW_DATA_LOSS option. If it stills gives you errors, then I hope you have backups to restore from.

  • Hi Rcosta,

    can you pl. provide me the complete sytax ro command for me to do that. Thnaks fro your help.

  • You should read in BOL the available options, check REPAIR_REBUILD option wich is more secure or REPAIR_ALLOW_DATA_LOSS)

    You should run from QA:

    DBCC CHECKDB ('DbName', REPAIR_REBUILD)

    If is not very time consuming, I would run first the option Repair Rebuild and if it still fails then REPAIR_ALLOW_DATA_LOSS.

    If all this fails, you should restore from the last backup.

    Do you have a good recent backup to restore from?

  • Rcosta,

    Thanks for your help. Yes I do have good recent backup.

  • If it fails and you need help with the restore process, here is many people who can give you advice.

    Good luck!

  • I found that reindexing can help reduce these errors. If it doesn't, drop and create the index on the offending table(s). See if the offending tables have clustered indexes - they help a lot.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply