SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Data consistency errors
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

sindhigrl
Starting Member

USA
3 Posts

Posted - 04/27/2006 :  11:02:20  Show Profile  Send sindhigrl an AOL message  Click to see sindhigrl's MSN Messenger address  Reply with Quote
Can anyone please tell me why I recieved these errors when running dbcc check db. Thank god it was a user created "test" table in a production database and I was able to just drop the table and rerun dbcc with no errors, but this is the second time this has happened in the last month(I just started this job the week of the first error)- and we ended up having to restore to the last good backup.

Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652192), slot 3, text ID 225434796032 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652192), slot 4, text ID 225434861568 is not referenced.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1543676547, index ID 255: Page (1:652193) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1543676547, index ID 255, page (1:652193). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 0, text ID 225434730496 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 1, text ID 225434927104 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 2, text ID 225434992640 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 3, text ID 225435058176 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 4, text ID 225435123712 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 5, text ID 225435189248 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 6, text ID 225435254784 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 7, text ID 225435320320 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 0, text ID 225435385856 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 1, text ID 225435451392 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 2, text ID 225435516928 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 3, text ID 225435582464 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 4, text ID 225435648000 is not referenced.
DBCC results for 'BILL_PRT_DETAIL'.
There are 909154 rows in 101409 pages for object 'BILL_PRT_DETAIL'.
DBCC results for 'BILLG_ERR_MSGS'.
There are 971 rows in 52 pages for object 'BILLG_ERR_MSGS'.
DBCC results for 'WORK_COMPCY_LEVEL'.
There are 0 rows in 0 pages for object 'WORK_COMPCY_LEVEL'.
DBCC results for 'BILL_PRT_HEADER'.
There are 196396 rows in 24550 pages for object 'BILL_PRT_HEADER'.
DBCC results for 'WORK_COMPCY_TYPE'.
There are 0 rows in 0 pages for object 'WORK_COMPCY_TYPE'.
DBCC results for 'BILL_PRT_MSGS'.
There are 0 rows in 0 pages for object 'BILL_PRT_MSGS'.
DBCC results for 'MTR_TMP_DTA_SEL'.
There are 0 rows in 0 pages for object 'MTR_TMP_DTA_SEL'.
DBCC results for 'WORK_IN_PROGRESS'.
There are 1 rows in 1 pages for object 'WORK_IN_PROGRESS'.
DBCC results for 'BILL_PYMT'.
There are 750053 rows in 19951 pages for object 'BILL_PYMT'.
DBCC results for 'NOTES'.
There are 26812 rows in 457 pages for object 'NOTES'.
DBCC results for 'WORK_ORDER_MASTER'.
There are 0 rows in 0 pages for object 'WORK_ORDER_MASTER'.
DBCC results for 'BUD_BILLG_AMT'.
There are 0 rows in 0 pages for object 'BUD_BILLG_AMT'.
DBCC results for 'NOTES_RELSHP'.
There are 22428 rows in 252 pages for object 'NOTES_RELSHP'.
DBCC results for 'WO_ACT_STAT'.
There are 0 rows in 0 pages for object 'WO_ACT_STAT'.
DBCC results for 'BUD_BILLG_CNSM_HST'.
There are 0 rows in 0 pages for object 'BUD_BILLG_CNSM_HST'.
DBCC results for 'NXT_NBR'.
There are 7 rows in 1 pages for object 'NXT_NBR'.
DBCC results for 'WO_ADDTNL_INFO'.
There are 0 rows in 0 pages for object 'WO_ADDTNL_INFO'.
DBCC results for 'BUD_BILLG_HST'.
There are 0 rows in 0 pages for object 'BUD_BILLG_HST'.
DBCC results for 'PARENT_HST'.
There are 0 rows in 0 pages for object 'PARENT_HST'.
DBCC results for 'WO_APPVL_ROUTING'.
There are 0 rows in 0 pages for object 'WO_APPVL_ROUTING'.
DBCC results for 'BUD_BILLG_WTHR_HST'.
There are 0 rows in 0 pages for object 'BUD_BILLG_WTHR_HST'.
DBCC results for 'PHY_ADDR'.
There are 70776 rows in 7905 pages for object 'PHY_ADDR'.
DBCC results for 'WO_BEHAVIOR_RULE'.
There are 0 rows in 0 pages for object 'WO_BEHAVIOR_RULE'.
DBCC results for 'BUD_BILLG_WTHR_SEV'.
There are 0 rows in 0 pages for object 'BUD_BILLG_WTHR_SEV'.
DBCC results for 'POSTAL_TOWN_CD'.
There are 29539 rows in 569 pages for object 'POSTAL_TOWN_CD'.
DBCC results for 'WO_COMPONENTS'.
There are 0 rows in 0 pages for object 'WO_COMPONENTS'.
DBCC results for 'BUS_UNT'.
There are 1310 rows in 25 pages for object 'BUS_UNT'.
DBCC results for 'cash match'.
There are 738871 rows in 6720 pages for object 'cash match'.
DBCC results for 'POSTED_HISTORY'.
There are 1230436 rows in 26768 pages for object 'POSTED_HISTORY'.
DBCC results for 'WO_CONSTANTS'.
There are 0 rows in 0 pages for object 'WO_CONSTANTS'.
DBCC results for 'BUS_UNT_MSTR'.
There are 0 rows in 0 pages for object 'BUS_UNT_MSTR'.
DBCC results for 'Cashmatch7_30'.
There are 727509 rows in 6619 pages for object 'Cashmatch7_30'.
DBCC results for 'PROFILE_CAT'.
There are 0 rows in 0 pages for object 'PROFILE_CAT'.
DBCC results for 'WO_EDIT_RULE'.
There are 0 rows in 0 pages for object 'WO_EDIT_RULE'.
DBCC results for 'CNSMPTN_SVC_CONTN'.
There are 36776 rows in 928 pages for object 'CNSMPTN_SVC_CONTN'.
DBCC results for 'Trace_cash_match'.
There are 815011 rows in 7412 pages for object 'Trace_cash_match'.
DBCC results for 'PROOF_BILL_PRT_DTL'.
There are 0 rows in 0 pages for object 'PROOF_BILL_PRT_DTL'.
DBCC results for 'WO_MASTER_FILE'.
There are 0 rows in 0 pages for object 'WO_MASTER_FILE'.
DBCC results for 'cash match 8-24'.
There are 815011 rows in 7414 pages for object 'cash match 8-24'.
CHECKDB found 0 allocation errors and 17 consistency errors in table 'cash match 8-24' (object ID 1543676547).
DBCC results for 'PROOF_BILL_PRT_HDR'.
There are 0 rows in 0 pages for object 'PROOF_BILL_PRT_HDR'.
DBCC results for 'CNVRGT_BILLG_DTL'.
There are 0 rows in 0 pages for object 'CNVRGT_BILLG_DTL'.
DBCC results for 'WO_RTG_APPVL_MSTR'.
There are 0 rows in 0 pages for object 'WO_RTG_APPVL_MSTR'.
DBCC results for 'PYMT_TERMS'.
There are 2 rows in 1 pages for object 'PYMT_TERMS'.
DBCC results for 'CNVRGT_BILLG_HDR'.
There are 0 rows in 0 pages for object 'CNVRGT_BILLG_HDR'.
DBCC results for 'WO_STAT'.
There are 0 rows in 0 pages for object 'WO_STAT'.
DBCC results for 'Cash Matching Process'.
There are 836838 rows in 7612 pages for object 'Cash Matching Process'.
DBCC results for 'RD_CYCLE'.
There are 55 rows in 1 pages for object 'RD_CYCLE'.
DBCC results for 'WO_STAT_RULES'.
There are 0 rows in 0 pages for object 'WO_STAT_RULES'.
DBCC results for 'REASON_CD'.
There are 0 rows in 0 pages for object 'REASON_CD'.
DBCC results for 'WO_TYP'.
There are 0 rows in 0 pages for object 'WO_TYP'.
DBCC results for 'COLCT_RULES'.
There are 30 rows in 1 pages for object 'COLCT_RULES'.
DBCC results for 'RECEIPTS_BTCH'.
There are 2109 rows in 44 pages for object 'RECEIPTS_BTCH'.
DBCC results for 'nightly107'.
There are 344086 rows in 3225 pages for object 'nightly107'.
DBCC results for 'WO_TYP_ACT_STAT'.
There are 0 rows in 0 pages for object 'WO_TYP_ACT_STAT'.
DBCC results for 'COMPONENT_MASTER'.
There are 0 rows in 0 pages for object 'COMPONENT_MASTER'.
DBCC results for 'RECEIPTS_I_FILE'.
There are 51698 rows in 3244 pages for object 'RECEIPTS_I_FILE'.
DBCC results for 'NightCash10-12'.
There are 64657 rows in 592 pages for object 'NightCash10-12'.
DBCC results for 'WRK_CENTER_WRK_SCH'.
There are 0 rows in 0 pages for object 'WRK_CENTER_WRK_SCH'.
DBCC results for 'CONS_SVC_CONN_CD'.
There are 1524 rows in 20 pages for object 'CONS_SVC_CONN_CD'.
DBCC results for 'RECEIPT_ITM'.
There are 151581 rows in 6334 pages for object 'RECEIPT_ITM'.
DBCC results for 'Utiligy Cash Match Trace'.
There are 321627 rows in 2928 pages for object 'Utiligy Cash Match Trace'.
DBCC results for 'WRTOFF_GL_CLASS_CD'.
There are 0 rows in 0 pages for object 'WRTOFF_GL_CLASS_CD'.
DBCC results for 'CONTACT_INFO'.
There are 1 rows in 1 pages for object 'CONTACT_INFO'.
DBCC results for 'REFUND_HISTORY'.
There are 906 rows in 24 pages for object 'REFUND_HISTORY'.
DBCC results for 'RECEIPTS_I_FILE2'.
There are 48343 rows in 3022 pages for object 'RECEIPTS_I_FILE2'.
DBCC results for 'CUST_ADDR_REL'.
There are 70611 rows in 2258 pages for object 'CUST_ADDR_REL'.
DBCC results for 'REPORT_TYPE'.
There are 42 rows in 1 pages for object 'REPORT_TYPE'.
DBCC results for 'CUST_CNTRCT_RELSHP'.
There are 0 rows in 0 pages for object 'CUST_CNTRCT_RELSHP'.
DBCC results for 'REQ_READ_SCH'.
There are 1 rows in 1 pages for object 'REQ_READ_SCH'.
DBCC results for 'RESOURCE_ASGNDS'.
There are 0 rows in 0 pages for object 'RESOURCE_ASGNDS'.
DBCC results for 'CUST_INFO'.
There are 36779 rows in 2480 pages for object 'CUST_INFO'.
DBCC results for 'RESOURCE_MASTER'.
There are 0 rows in 0 pages for object 'RESOURCE_MASTER'.
DBCC results for 'RESOURCE_WORK_SCH'.
There are 0 rows in 0 pages for object 'RESOURCE_WORK_SCH'.
DBCC results for 'CUST_PYMT_ACCT'.
There are 0 rows in 0 pages for object 'CUST_PYMT_ACCT'.
DBCC results for 'ROUTE'.
There are 95 rows in 2 pages for object 'ROUTE'.
DBCC results for 'ADDR'.
There are 70767 rows in 861 pages for object 'ADDR'.
DBCC results for 'CUST_STMT_HST'.
There are 0 rows in 0 pages for object 'CUST_STMT_HST'.
DBCC results for 'ROUTE_RD_CYCLE'.
There are 0 rows in 0 pages for object 'ROUTE_RD_CYCLE'.
DBCC results for 'AGING_DAYS_TBL'.
There are 5 rows in 1 pages for object 'AGING_DAYS_TBL'.
DBCC results for 'CUST_SVC_RELSHP'.
There are 73551 rows in 1415 pages for object 'CUST_SVC_RELSHP'.
DBCC results for 'RPT_TYPE_CRITERIA'.
There are 116 rows in 2 pages for object 'RPT_TYPE_CRITERIA'.
DBCC results for 'AMX_MSG_LG'.
There are 0 rows in 0 pages for object 'AMX_MSG_LG'.
DBCC results for 'RPT_VERSION'.
There are 32 rows in 1 pages for object 'RPT_VERSION'.
DBCC results for 'DED_MTR_CONSUM'.
There are 0 rows in 0 pages for object 'DED_MTR_CONSUM'.
DBCC results for 'ASGND_BILL_CAT_CD'.
There are 0 rows in 0 pages for object 'ASGND_BILL_CAT_CD'.
DBCC results for 'RPT_VRSN_CRITERIA'.
There are 15 rows in 1 pages for object 'RPT_VRSN_CRITERIA'.
DBCC results for 'DED_MTR_POS'.
There are 0 rows in 0 pages for object 'DED_MTR_POS'.
DBCC results for 'ASGND_CUST_CAT_CD'.
There are 0 rows in 0 pages for object 'ASGND_CUST_CAT_CD'.
DBCC results for 'SCH_POOL'.
There are 0 rows in 0 pages for object 'SCH_POOL'.
DBCC results for 'DED_MTR_RDING_HIST'.
There are 0 rows in 0 pages for object 'DED_MTR_RDING_HIST'.
CHECKDB found 0 allocation errors and 17 consistency errors in database 'UtiligyPD'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (UtiligyPD ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.


Thanks!
Anita

ryanston
Microsoft SQL Server Product Team

USA
89 Posts

Posted - 04/27/2006 :  14:29:44  Show Profile  Visit ryanston's Homepage  Reply with Quote
You need to check your hardware.

The most important error(s) returned are the ones below - all of the other errors are a result of the failure to read page 1:652193.

quote:

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1543676547, index ID 255: Page (1:652193) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1543676547, index ID 255, page (1:652193). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.


The 8939 error indicates that we couldn't read the page because an IO error was returned during the read operation. The IO error code is -1, which is an internal error code that translates to a TORN PAGE error. Take a look at the Books Online topic for torn pages:

quote:

TORN_PAGE_DETECTION

This recovery option allows SQL Server to detect incomplete I/O operations caused by power failures or other system outages.

When set to ON, this option causes a bit to be reversed for each 512-byte sector in an 8-kilobyte (KB) database page when the page is written to disk. If a bit is in the wrong state when the page is later read by SQL Server, the page was written incorrectly; a torn page is detected. Torn pages are usually detected during recovery because any page that was written incorrectly is likely to be read by recovery.

Although SQL Server database pages are 8 KB, disks perform I/O operations using a 512-byte sector. Therefore, 16 sectors are written per database page. A torn page can occur if the system fails (for example, due to power failure) between the time the operating system writes the first 512-byte sector to disk and the completion of the 8-KB I/O operation. If the first sector of a database page is successfully written before the failure, the database page on disk will appear as updated, although it may not have succeeded.

Note Using battery-backed disk caches can ensure that data is successfully written to disk or not written at all.

If a torn page is detected, an I/O error is raised and the connection is killed. If the torn page is detected during recovery, the database is also marked suspect. The database backup should be restored, and any transaction log backups applied, because it is physically inconsistent.


HTH!

----------------------
Ryan Stonecipher
Developer, Microsoft SQL Server Storage Engine, DBCC
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page

sindhigrl
Starting Member

USA
3 Posts

Posted - 04/27/2006 :  15:29:10  Show Profile  Send sindhigrl an AOL message  Click to see sindhigrl's MSN Messenger address  Reply with Quote
Thanks Ryan. I'll have our server guys look into it. I have another question too...Right now I'm doing a dbcc checkdb before our full backups every night, but should I also be doing one before every hourly tlog backup to prevent data loss or do you think that's overkill?

Thanks!
Anita
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
35951 Posts

Posted - 04/27/2006 :  15:33:37  Show Profile  Visit tkizer's Homepage  Reply with Quote
Hopefully you don't have the repair option as part of your DBCC CHECKDB command. Daily consistency check is fine. Are you taking an action when the DBCC CHECKDB job fails? Notification to the DBAs?

Tara Kizer
aka tduggan
Go to Top of Page

sindhigrl
Starting Member

USA
3 Posts

Posted - 04/27/2006 :  15:41:00  Show Profile  Send sindhigrl an AOL message  Click to see sindhigrl's MSN Messenger address  Reply with Quote
No I don't have a repair option. I have the dbcc checkdb as step one in my backup job and if it fails I have it set to page me on my cell-so in case of failure the full nightly backup doesn't run till we manually start it.

Thanks!
Anita
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
35951 Posts

Posted - 04/27/2006 :  15:45:43  Show Profile  Visit tkizer's Homepage  Reply with Quote
Since you are paging yourself when the DBCC CHECKDB job fails, you might want to run it a couple of times per day until your hardware problems (indicated by Ryan due to the DBCC CHECKDB output) are resolved. It is going to add an extra bit of load on the database server, so you need to keep this in mind. How long does it take to run generally?

If you didn't have hardware problems, then nightly DBCC CHECKDB would be fine. This is what we do.

Tara Kizer
aka tduggan
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.14 seconds. Powered By: Snitz Forums 2000