DBCC CHECKDB errors
-
Hi,
I found 4 errors while running DBCC CHECKDB(db). See the error details below. How do I correct it. If I need to run CHECKDB with REPAIR_REBUILD I need the database to be in single user mode. This is a production box. Any other ideas.
DBCC results for 'eLocator_repl'.
DBCC results for 'sysobjects'.
There are 90 rows in 1 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 106 rows in 7 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 550 rows in 11 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 135 rows in 17 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 56 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 23 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 327 rows in 2 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 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 'countries'.
There are 31 rows in 1 pages for object 'countries'.
DBCC results for 'cons_icon'.
There are 357 rows in 3 pages for object 'cons_icon'.
DBCC results for 'cons_pcat'.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:28231) allocated to object ID 1349579846, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
There are 474 rows in 2 pages for object 'cons_pcat'.
DBCC results for 'cons_rstmtc'.
There are 61 rows in 4 pages for object 'cons_rstmtc'.
DBCC results for 'cons_icont'.
There are 383 rows in 5 pages for object 'cons_icont'.
DBCC results for 'cons_rstmt'.
There are 89 rows in 5 pages for object 'cons_rstmt'.
DBCC results for 'cons_src'.
There are 58 rows in 2 pages for object 'cons_src'.
DBCC results for 'cons_vm'.
There are 41 rows in 2 pages for object 'cons_vm'.
DBCC results for 'cons_vms'.
There are 41 rows in 2 pages for object 'cons_vms'.
DBCC results for 'cons_pcatt'.
There are 527 rows in 7 pages for object 'cons_pcatt'.
DBCC results for 'FULL_Live_Rules_and_Applications'.
There are 13137 rows in 257 pages for object 'FULL_Live_Rules_and_Applications'.
DBCC results for 'ErrLog'.
There are 303 rows in 2 pages for object 'ErrLog'.
DBCC results for 'FULL_Preview_Rules_and_Applications'.
There are 13085 rows in 256 pages for object 'FULL_Preview_Rules_and_Applications'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'FULL_Preview_Rules_and_Applications' (object ID 1349579846).
DBCC results for 'cons_pl'.
There are 2525 rows in 8 pages for object 'cons_pl'.
DBCC results for 'cons_plt'.
There are 2202 rows in 27 pages for object 'cons_plt'.
DBCC results for 'ELOC_rs1_not_needed_anymore'.
There are 41659 rows in 700 pages for object 'ELOC_rs1_not_needed_anymore'.
DBCC results for 'ELOC_rs2_not_needed_anymore'.
Server: Msg 2534, Level 16, State 2, Line 1
Table error: Page (1:28231) with object ID 1653580929, index ID 3 in its header is allocated by another object.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1653580929, index ID 3. Page (1:28231) is missing references from parent (unknown) and previous (page (1:28230)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 1653580929, index ID 3. The next pointer of (1:28231) refers to page (1:28232). Neither (1:28232) nor its parent were encountered. Possible bad chain linkage.
There are 886398 rows in 5622 pages for object 'ELOC_rs2_not_needed_anymore'.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'ELOC_rs2_not_needed_anymore' (object ID 1653580929).
DBCC results for 'ELOC_rs3_not_needed_anymore'.
There are 862234 rows in 3206 pages for object 'ELOC_rs3_not_needed_anymore'.
DBCC results for 'cs_tmpRS2'.
There are 38930 rows in 97 pages for object 'cs_tmpRS2'.
DBCC results for 'cs_PPro-Programs'.
There are 836927 rows in 6366 pages for object 'cs_PPro-Programs'.
DBCC results for 'KWTRANS'.
There are 296 rows in 4 pages for object 'KWTRANS'.
DBCC results for 'cs_PPro-Partners'.
There are 515914 rows in 4479 pages for object 'cs_PPro-Partners'.
DBCC results for 'fakesellout'.
There are 1304 rows in 6 pages for object 'fakesellout'.
DBCC results for 'cons_rr'.
There are 41 rows in 1 pages for object 'cons_rr'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 'FULL_Preview_Rules_and_Applications_OLD'.
There are 13133 rows in 224 pages for object 'FULL_Preview_Rules_and_Applications_OLD'.
DBCC results for 'FULL_Live_Rules_and_Applications_OLD'.
There are 13133 rows in 224 pages for object 'FULL_Live_Rules_and_Applications_OLD'.
CHECKDB found 0 allocation errors and 4 consistency errors in database 'eLocator_repl'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (eLocator_repl ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me -
You will need to take the database offline and repair these errors. Continuing to use the database when it has consistency errors could compound the problem possibly even leading to unrecoverable database corruption.
You can minimise the downtime by running DBCC CHECKTABLE instead of DBCC CHECKDB. This just targets the individual table instead of every table in the database.
As indicated by the second last message,
"repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (eLocator_repl )."
You'll need to run DBCC command with the REPAIR_ALLOW_DATA_LOSS option.
Make sure you have a full database backup before running the command. Once the errors have been corrected, check for data loss. The REPAIR_ALLOW_DATA_LOSS option doesn't necessarily mean that data will be lost. If you do find that some data is missing you'll need to decide if you recreate the missing information, or restore your backup to a seperate database and try to transfer the data from it.
--------------------
Colt 45 - the original point and click interface
-
Thanks a lot Phill Carter. I was planning to do a repair_rebuild. Any way waiting for the customer to get back before taking the database offline
Itz helpful
Cheers
Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply