Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 DBCC consistency errors

Author  Topic 

louigom
Starting Member

8 Posts

Posted - 2005-12-12 : 09:47:59
I would need help to debug the following allocation errors on DBCC:

Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958608) object ID 16 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:985853) object ID 16 index ID 2 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958600) object ID 16 index ID 255 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1067763) object ID 17 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1120026) object ID 17 index ID 2 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1154482) object ID 17 index ID 3 but was not detected in the scan. [SQLSTATE 42000]
Msg 2536, Sev 16: DBCC results for 'SalesHistoryDB'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysobjects'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 289 rows in 7 pages for object 'sysobjects'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysindexes'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 277 rows in 19 pages for object 'sysindexes'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syscolumns'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1809 rows in 43 pages for object 'syscolumns'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'systypes'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syscomments'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 301 rows in 101 pages for object 'syscomments'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysfiles1'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syspermissions'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 311 rows in 3 pages for object 'syspermissions'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysusers'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysproperties'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 199 rows in 6 pages for object 'sysproperties'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysdepends'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1768 rows in 11 pages for object 'sysdepends'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysreferences'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 16)' (object ID 16). [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 17)' (object ID 17). [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
DBCC results for 'IgnoreSalesRep'. [SQLSTATE 01000]
There are 406 rows in 2 pages for object 'IgnoreSalesRep'. [SQLSTATE 01000]
DBCC results for 'invnsrc'. [SQLSTATE 01000]
There are 6101966 rows in 15067 pages for object 'invnsrc'. [SQLSTATE 01000]
DBCC results for 'INVO_ERRS'. [SQLSTATE 01000]
There are 333 rows in 12 pages for object 'INVO_ERRS'. [SQLSTATE 01000]
DBCC results for 'INVO_ERRS_old'. [SQLSTATE 01000]
There are 152 rows in 3 pages for object 'INVO_ERRS_old'. [SQLSTATE 01000]
DBCC results for 'INVO_HIST'. [SQLSTATE 01000]
There are 55159551 rows in 937501 pages for object 'INVO_HIST'. [SQLSTATE 01000]
DBCC results for 'INVO_HIST_SMALL'. [SQLSTATE 01000]
There are 1124659 rows in 21220 pages for object 'INVO_HIST_SMALL'. [SQLSTATE 01000]
DBCC results for 'InvoiceHistory'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'InvoiceHistory'. [SQLSTATE 01000]
DBCC results for 'QUAR_INVO_HIST'. [SQLSTATE 01000]
There are 1430739 rows in 5379 pages for object 'QUAR_INVO_HIST'. [SQLSTATE 01000]
DBCC results for 'MARKETING_REPORTS'. [SQLSTATE 01000]
There are 36371 rows in 151 pages for object 'MARKETING_REPORTS'. [SQLSTATE 01000]
DBCC results for 'MKP90'. [SQLSTATE 01000]
There are 36030746 rows in 205890 pages for object 'MKP90'. [SQLSTATE 01000]
DBCC results for 'MR_CLASS_MANU'. [SQLSTATE 01000]
There are 12159 rows in 46 pages for object 'MR_CLASS_MANU'. [SQLSTATE 01000]
DBCC results for 'MR_GROUP_MANU'. [SQLSTATE 01000]
There are 16889 rows in 66 pages for object 'MR_GROUP_MANU'. [SQLSTATE 01000]
DBCC results for 'MR_MANU_CLASS'. [SQLSTATE 01000]
There are 4876 rows in 19 pages for object 'MR_MANU_CLASS'. [SQLSTATE 01000]
DBCC results for 'MR_MANU_GROUP'. [SQLSTATE 01000]
There are 15565 rows in 61 pages for object 'MR_MANU_GROUP'. [SQLSTATE 01000]
DBCC results for 'PseudoLeaders'. [SQLSTATE 01000]
There are 79 rows in 2 pages for object 'PseudoLeaders'. [SQLSTATE 01000]
DBCC results for 'InvoiceHeader'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'InvoiceHeader'. [SQLSTATE 01000]
DBCC results for 'FedTeamGoals'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'FedTeamGoals'. [SQLSTATE 01000]
DBCC results for 'SALES_MODIFIER'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'SALES_MODIFIER'. [SQLSTATE 01000]
DBCC results for 'FedTeamPlayers'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'FedTeamPlayers'. [SQLSTATE 01000]
DBCC results for 'CGTempWMS'. [SQLSTATE 01000]
There are 25 rows in 1 pages for object 'CGTempWMS'. [SQLSTATE 01000]
DBCC results for 'srcinvn'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'srcinvn'. [SQLSTATE 01000]
DBCC results for 'TEMP_ExtranetData'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'TEMP_ExtranetData'. [SQLSTATE 01000]
DBCC results for 'EMP10'. [SQLSTATE 01000]
There are 113373 rows in 1471 pages for object 'EMP10'. [SQLSTATE 01000]
DBCC results for 'EMP10_UNIQUE'. [SQLSTATE 01000]
There are 18947 rows in 245 pages for object 'EMP10_UNIQUE'. [SQLSTATE 01000]
DBCC results for 'ITEM_SALES_306090'. [SQLSTATE 01000]
There are 310629 rows in 929 pages for object 'ITEM_SALES_306090'. [SQLSTATE 01000]
DBCC results for 'temp_SalesSummaryData'. [SQLSTATE 01000]
There are 45781 rows in 751 pages for object 'temp_SalesSummaryData'. [SQLSTATE 01000]
DBCC results for 'Rob_DeletedFromCustomerPricingMatrix20031107'. [SQLSTATE 01000]
There are 1469 rows in 6 pages for object 'Rob_DeletedFromCustomerPricingMatrix20031107'. [SQLSTATE 01000]
DBCC results for 'COMMISSION_ADJ'. [SQLSTATE 01000]
There are 1645553 rows in 37801 pages for object 'COMMISSION_ADJ'. [SQLSTATE 01000]
DBCC results for 'SalesSummaryData'. [SQLSTATE 01000]
There are 2288331 rows in 36372 pages for object 'SalesSummaryData'. [SQLSTATE 01000]
DBCC results for 'CDW_CODB'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'CDW_CODB'. [SQLSTATE 01000]
DBCC results for 'dtproperties'. [SQLSTATE 01000]
There are 14 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000]
DBCC results for 'Temp_SalesData_new'. [SQLSTATE 01000]
There are 7275 rows in 94 pages for object 'Temp_SalesData_new'. [SQLSTATE 01000]
DBCC results for 'MKP97'. [SQLSTATE 01000]
There are 818535 rows in 6628 pages for object 'MKP97'. [SQLSTATE 01000]
DBCC results for 'MARKETING_REPORTS_Saved'. [SQLSTATE 01000]
There are 28431 rows in 113 pages for object 'MARKETING_REPORTS_Saved'. [SQLSTATE 01000]
DBCC results for 'Commission_Adjustment'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'Commission_Adjustment'. [SQLSTATE 01000]
DBCC results for 'F1730A'. [SQLSTATE 01000]
There are 1124104 rows in 16059 pages for object 'F1730A'. [SQLSTATE 01000]
DBCC results for 'OEP80U'. [SQLSTATE 01000]
There are 1357451 rows in 11634 pages for object 'OEP80U'. [SQLSTATE 01000]
DBCC results for 'OE40LN'. [SQLSTATE 01000]
There are 1281910 rows in 10155 pages for object 'OE40LN'. [SQLSTATE 01000]
DBCC results for 'sysarticles'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'sysarticles'. [SQLSTATE 01000]
DBCC results for 'sysschemaarticles'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysschemaarticles'. [SQLSTATE 01000]
DBCC results for 'syspublications'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'syspublications'. [SQLSTATE 01000]
DBCC results for 'CommissionGoalsRange'. [SQLSTATE 01000]
There are 12 rows in 1 pages for object 'CommissionGoalsRange'. [SQLSTATE 01000]
DBCC results for 'LOSGoals'. [SQLSTATE 01000]
There are 107 rows in 1 pages for object 'LOSGoals'. [SQLSTATE 01000]
DBCC results for 'OrderInstallInfo'. [SQLSTATE 01000]
There are 318699 rows in 1241 pages for object 'OrderInstallInfo'. [SQLSTATE 01000]
DBCC results for 'syssubscriptions'. [SQLSTATE 01000]
There are 4 rows in 1 pages for object 'syssubscriptions'. [SQLSTATE 01000]
DBCC results for 'sysarticleupdates'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysarticleupdates'. [SQLSTATE 01000]
DBCC results for 'MSpub_identity_range'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'MSpub_identity_range'. [SQLSTATE 01000]
DBCC results for 'systranschemas'. [SQLSTATE 01000]
Msg 2576, Sev 16: IAM page (1:1170538) is pointed to by the previous pointer of IAM page (1:1170540) object ID 1583344705 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 8947, Sev 16: Table error: Multiple IAM pages for object ID 1583344705, index ID 0 contain allocations for the same interval. IAM pages (1:1170540) and (1:2502333). [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (1:2502332) is pointed to by the previous pointer of IAM page (1:2502333) object ID 1583344705 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'systranschemas'. [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 1583344705)' (object ID 1583344705). [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'DummyTrans'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'DummyTrans'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'InvoiceDownloadCheck'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 9 rows in 1 pages for object 'InvoiceDownloadCheck'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'ORDER_HIST_MUNICH'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'ORDER_HIST_MUNICH'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'ACTIONS'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 3864063 rows in 43417 pages for object 'ACTIONS'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CALLVOLUME_REQ'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 24 rows in 1 pages for object 'CALLVOLUME_REQ'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'COMMISH_GOALS'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 273 rows in 2 pages for object 'COMMISH_GOALS'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CM210X'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1826290 rows in 97778 pages for object 'CM210X'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CM30'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 96 rows in 1 pages for object 'CM30'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CM31'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 32 rows in 1 pages for object 'CM31'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'COMMISSION_ADJ_INDEX'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1 rows in 1 pages for object 'COMMISSION_ADJ_INDEX'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'COMMISSION_DAILY'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1659173 rows in 17841 pages for object 'COMMISSION_DAILY'. [SQLSTATE 01000]
DBCC results for 'COMMISSION_EMP'. [SQLSTATE 01000]
There are 12080 rows in 58 pages for object 'COMMISSION_EMP'. [SQLSTATE 01000]
DBCC results for 'CUST_INVO_SUMMARY'. [SQLSTATE 01000]
There are 9512732 rows in 65156 pages for object 'CUST_INVO_SUMMARY'. [SQLSTATE 01000]
DBCC results for 'DAILY_PHONE'. [SQLSTATE 01000]
There are 1918105 rows in 20566 pages for object 'DAILY_PHONE'. [SQLSTATE 01000]
DBCC results for 'Dates2Run'. [SQLSTATE 01000]
There are 31 rows in 1 pages for object 'Dates2Run'. [SQLSTATE 01000]
DBCC results for 'DAILY_PHONE_ERRORS'. [SQLSTATE 01000]
There are 1701 rows in 18 pages for object 'DAILY_PHONE_ERRORS'. [SQLSTATE 01000]
CHECKDB found 9 allocation errors and 0 consistency errors in database 'SalesHistoryDB'. [SQLSTATE 01000]
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (SalesHistoryDB ). [SQLSTATE 01000]
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-12 : 19:00:17
This looks like someone's deleted entries from sysindexes manually - do you know if this is the case?

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page

louigom
Starting Member

8 Posts

Posted - 2005-12-15 : 13:29:28
Paul,

Thank you very much for replying. I am not aware of anybody updating the sysindexes directly.
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-15 : 19:35:47
ok - all the errors are saying that there's no metadata for the IAM chains listed. IAM page (0:0) in the output basically means thelink to the firstIAM page in the IAM chain from the sysindexes row - hence my assumption.

Can you answer the following questions please:
1) do you have usable backups that will allo you to meet you data loss SLAs? (If not, why not?)
2) is there any evidence of h/w issues in the SQL errorlog or Windows event logs?
3) are all you h/w drivers/firmware up-to-date?
4) when did this start happening? Did any unusall occurence preceed it - like a power outage?
5) what version+SP are you on?

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page

louigom
Starting Member

8 Posts

Posted - 2005-12-16 : 14:33:34
1) do you have usable backups that will allow you to meet you data loss SLAs? (If not, why not?)

-- This DBCC error is currently happening since 12/03/05. We could go back to 12/02/05 but developers have to save copies of the DB changes they have done since.

2) is there any evidence of h/w issues in the SQL errorlog or Windows event logs?

-- No h/w issues on SQL errorlog or Windows event logs

3) are all you h/w drivers/firmware up-to-date?

-- very much so

4) when did this start happening? Did any unusall occurence preceed it - like a power outage?

-- no power outage. started 12/3/05

5) what version+SP are you on?

-- s2k with SP4
Go to Top of Page

louigom
Starting Member

8 Posts

Posted - 2005-12-29 : 13:08:29
Paul,

Any suggestions?

Thanks,
Louie
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-30 : 13:38:08
I've been on vacation - hence the delay in replying.

Considering the date when these started happening - did you run regular CHECKDBs before 12/3? When did you do the upgrade to SP4 (not that I'm saying SP4 is the problem)? Did the exact same set of errors exist on 12/3 or has the list of errors grown/shrunk?

There are some other IAM chain corruptions which are quite unusual. I've seen these before when someone's trashed a transaction log and left the database in a transactionally inconsistent state. Do you know if that's happened?

Do you have the SQL errorlogs that cover the window between last known good and first known bad CHECKDBs? If so, could you zip & email them to me to review?

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page
   

- Advertisement -