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
 dbcc REPAIR_ALLOW_DATA_LOSS
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

RonM
Starting Member

8 Posts

Posted - 08/01/2005 :  11:21:02  Show Profile  Reply with Quote
Paul
Thank you for reviewing

I see not hardware errors.
________________________________________________
Original

[14] Database MAGIC: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 2576: [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:3231) object ID 1397580017 index ID 24 but was not detected in the scan.

The following errors were found:

[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:3231) object ID 1397580017 index ID 24 but was not detected in the scan.

[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10127) object ID 1941581955 index ID 45 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 2 allocation errors and 0 consistency errors in table '_SMDBA_._PURCHSTAT_' (object ID 1733581214).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 1941581955)' (object ID 1941581955).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 60 allocation errors and 0 consistency errors in database 'MAGIC'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MAGIC ).
** Execution Time: 0 hrs, 0 mins, 27 secs **

_________________________________
DBCC CHECKDB After DBCC CHECKALLOC (magic1, repair_allow_data_loss)

Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1413580074, index ID 2. Page (1:25004) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1413580074, index ID 7. Page (1:45781) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1413580074, index ID 8. Page (1:45858) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1413580074, index ID 9. Page (1:10853) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1413580074, index ID 9. Page (1:41341) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1413580074, index ID 11. Page (1:45955) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 56. Page (1:10869) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 56. Page (1:50101) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50103) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 56. The next pointer of (1:50101) refers to page (1:50103). Neither (1:50103) nor its parent were encountered. Possible bad chain linkage.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50136) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 56. Index node page (0:0), slot 0 refers to child page (1:50136) and previous child (0:0), but they were not encountered.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50137) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50138) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50139) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50140) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 57. Page (1:12273) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50141) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50143) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50144) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 57. Index node page (0:0), slot 0 refers to child page (1:50144) and previous child (0:0), but they were not encountered.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50145) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50146) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50147) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50148) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 58. Page (1:12396) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50149) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50151) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50184) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 58. Index node page (0:0), slot 0 refers to child page (1:50184) and previous child (0:0), but they were not encountered.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50185) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50186) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50187) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50188) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 62. Page (1:45862) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50232) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50234) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50235) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1509580416, index ID 62. Index node page (0:0), slot 0 refers to child page (1:50235) and previous child (0:0), but they were not encountered.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50236) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50237) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50238) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:50239) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:48528), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1694681135, index ID 13. Page (1:45777) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1701581100, index ID 2. Page (1:45800) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1701581100, index ID 7. Page (1:45802) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1701581100, index ID 8. Page (1:45804) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1701581100, index ID 9. Page (1:45806) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1701581100, index ID 10. Page (1:45792) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
DBCC results for 'Magic1'.
DBCC results for 'sysobjects'.
There are 6605 rows in 91 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 1625 rows in 88 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 96096 rows in 1614 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 6207 rows in 929 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 25603 rows in 111 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 125 rows in 2 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 95863 rows in 479 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 40 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 'NAMSYSCTISEARCHVIEWS'.
There are 0 rows in 1 pages for object 'NAMSYSCTISEARCHVIEWS'.
DBCC results for 'NAMSYSCTIMATCHCOLS'.
There are 0 rows in 1 pages for object 'NAMSYSCTIMATCHCOLS'.
DBCC results for 'NAMSYSMETAEXTS'.
There are 4 rows in 1 pages for object 'NAMSYSMETAEXTS'.
DBCC results for 'NAMSYSMENUS'.
There are 65 rows in 1 pages for object 'NAMSYSMENUS'.
DBCC results for '_SMDBA_._FAQFDBACK_'.
There are 0 rows in 1 pages for object '_SMDBA_._FAQFDBACK_'.
DBCC results for 'NAMSYSMENUITEMS'.
There are 320 rows in 3 pages for object 'NAMSYSMENUITEMS'.
DBCC results for '_SMDBA_._UDSTATUS_'.
There are 3 rows in 1 pages for object '_SMDBA_._UDSTATUS_'.
DBCC results for '_SMDBA_.SCACTIONS'.
There are 12 rows in 2 pages for object '_SMDBA_.SCACTIONS'.
DBCC results for '_SMDBA_._SEVERITY_'.
There are 4 rows in 1 pages for object '_SMDBA_._SEVERITY_'.
DBCC results for 'NAMSYSMBLTEMPLATES'.
There are 55 rows in 1 pages for object 'NAMSYSMBLTEMPLATES'.
DBCC results for 'NAMSYSJOBQUEUE'.
There are 0 rows in 8 pages for object 'NAMSYSJOBQUEUE'.
DBCC results for '_SMDBA_.TCCMSPMTTERM'.
There are 34 rows in 2 pages for object '_SMDBA_.TCCMSPMTTERM'.
DBCC results for 'NAMSYSLOG'.
There are 13 rows in 8 pages for object 'NAMSYSLOG'.
DBCC results for 'NAMSYSNOTIFYINFO'.
There are 6 rows in 1 pages for object 'NAMSYSNOTIFYINFO'.
DBCC results for 'DUAL'.
There are 1 rows in 1 pages for object 'DUAL'.
DBCC results for '_SMDBA_._NOTIFY_'.
There are 0 rows in 1 pages for object '_SMDBA_._NOTIFY_'.
DBCC results for 'HOLIDAY'.
There are 9 rows in 1 pages for object 'HOLIDAY'.
DBCC results for 'NAMSYSMBLRULES'.
There are 102 rows in 3 pages for object 'NAMSYSMBLRULES'.
DBCC results for 'HOLIDAYLIVE'.
There are 230 rows in 3 pages for object 'HOLIDAYLIVE'.
DBCC results for 'NAMSYSMBLACTIONSETS'.
There are 102 rows in 1 pages for object 'NAMSYSMBLACTIONSETS'.
DBCC results for 'HOLIDAYSET'.
There are 3 rows in 1 pages for object 'HOLIDAYSET'.
DBCC results for 'NAMSYSCURRENCIES'.
There are 174 rows in 2 pages for object 'NAMSYSCURRENCIES'.
DBCC results for 'NAMSYSMBLCONDITIONSETS'.
There are 98 rows in 1 pages for object 'NAMSYSMBLCONDITIONSETS'.
DBCC results for 'HOLIDAYSETDETAILS'.
There are 19 rows in 1 pages for object 'HOLIDAYSETDETAILS'.
DBCC results for '_SMDBA_.CMSOFFCCODE'.
There are 8 rows in 1 pages for object '_SMDBA_.CMSOFFCCODE'.
DBCC results for 'NAMSYSCURREXCH'.
There are 12 rows in 1 pages for object 'NAMSYSCURREXCH'.
DBCC results for 'NAMSYSLISTENCFG'.
There are 0 rows in 1 pages for object 'NAMSYSLISTENCFG'.
DBCC results for 'NAMSYSASSIGNNAVIGATORS'.
There are 1 rows in 1 pages for object 'NAMSYSASSIGNNAVIGATORS'.
DBCC results for 'NAMSYSHTMLASSIGNS'.
There are 325 rows in 6 pages for object 'NAMSYSHTMLASSIGNS'.
DBCC results for 'NAMSYSCSMESSAGES'.
There are 777 rows in 6 pages for object 'NAMSYSCSMESSAGES'.
DBCC results for '_SMDBA_._SMTPEMAIL_'.
There are 0 rows in 1 pages for object '_SMDBA_._SMTPEMAIL_'.
DBCC results for 'NAMSYSDBINFO'.
There are 389 rows in 10 pages for object 'NAMSYSDBINFO'.
DBCC results for '_SMDBA_._VENDORS_'.
There are 506 rows in 17 pages for object '_SMDBA_._VENDORS_'.
DBCC results for 'NAMSYSNAVGEN'.
There are 13 rows in 2 pages for object 'NAMSYSNAVGEN'.
DBCC results for '_SMDBA_._MAPIEMAIL_'.
There are 0 rows in 9 pages for object '_SMDBA_._MAPIEMAIL_'.
DBCC results for 'NAMSYSFOLDERINFO'.
There are 6558 rows in 49 pages for object 'NAMSYSFOLDERINFO'.
DBCC results for '_SMDBA_._POWERPAGE_'.
There are 0 rows in 1 pages for object '_SMDBA_._POWERPAGE_'.
DBCC results for 'NAMSYSHDTYPE'.
There are 1 rows in 1 pages for object 'NAMSYSHDTYPE'.
DBCC results for '_SMDBA_._WSLINK_'.
There are 0 rows in 0 pages for object '_SMDBA_._WSLINK_'.
DBCC results for '_SMDBA_._NETSEND_'.
There are 0 rows in 1 pages for object '_SMDBA_._NETSEND_'.
DBCC results for 'NAMSYSHTMLFORMS'.
There are 145 rows in 4 pages for object 'NAMSYSHTMLFORMS'.
DBCC results for '_SMDBA_._FAQCAT_'.
There are 0 rows in 1 pages for object '_SMDBA_._FAQCAT_'.
DBCC results for '_SMDBA_._TELALERT_'.
There are 0 rows in 1 pages for object '_SMDBA_._TELALERT_'.
DBCC results for '_SMDBA_._PI_'.
There are 9 rows in 1 pages for object '_SMDBA_._PI_'.
DBCC results for 'NAMSYSHTMLNAVIGATORS'.
There are 7 rows in 1 pages for object 'NAMSYSHTMLNAVIGATORS'.
DBCC results for 'NAMSYSCTIDEVICES'.
There are 0 rows in 0 pages for object 'NAMSYSCTIDEVICES'.
DBCC results for 'NAMSYSINVSRC'.
There are 0 rows in 0 pages for object 'NAMSYSINVSRC'.
DBCC results for 'NAMSYSCTILOG'.
There are 0 rows in 0 pages for object 'NAMSYSCTILOG'.
DBCC results for '_SMDBA_.TCGLCATEGORY'.
There are 2 rows in 1 pages for object '_SMDBA_.TCGLCATEGORY'.
DBCC results for 'NAMSYSLOGIC'.
There are 36 rows in 3 pages for object 'NAMSYSLOGIC'.
DBCC results for 'NAMSYSRECLOCK'.
There are 1 rows in 6 pages for object 'NAMSYSRECLOCK'.
DBCC results for 'NAMSYSMAC2SRC'.
There are 0 rows in 0 pages for object 'NAMSYSMAC2SRC'.
DBCC results for '_SMDBA_._PR_'.
There are 7 rows in 1 pages for object '_SMDBA_._PR_'.
DBCC results for 'NAMSYSMOD2MAC'.
There are 0 rows in 0 pages for object 'NAMSYSMOD2MAC'.
DBCC results for 'NAMSYSREPORT'.
There are 133 rows in 2 pages for object 'NAMSYSREPORT'.
DBCC results for 'NAMSYSREPORTDETAILS'.
There are 308 rows in 2 pages for object 'NAMSYSREPORTDETAILS'.
DBCC results for 'NAMSYSRULES'.
There are 1 rows in 1 pages for object 'NAMSYSRULES'.
DBCC results for 'NAMSYSSELFSERVICECONFIG'.
There are 0 rows in 1 pages for object 'NAMSYSSELFSERVICECONFIG'.
DBCC results for '_SMDBA_.CMSPROFCOD'.
There are 11 rows in 1 pages for object '_SMDBA_.CMSPROFCOD'.
DBCC results for 'NAMSYSTABINFO'.
There are 1065 rows in 18 pages for object 'NAMSYSTABINFO'.
DBCC results for 'NAMSYSTABLES'.
There are 50 rows in 2 pages for object 'NAMSYSTABLES'.
DBCC results for 'NAMSYSWOGENERATORS'.
There are 0 rows in 0 pages for object 'NAMSYSWOGENERATORS'.
DBCC results for 'NAMSYSWOTEMPLATES'.
There are 0 rows in 1 pages for object 'NAMSYSWOTEMPLATES'.
DBCC results for 'SMSYSEMAILREPLIES'.
There are 7 rows in 1 pages for object 'SMSYSEMAILREPLIES'.
DBCC results for '_SMDBA_._CATALOG_'.
There are 289 rows in 8 pages for object '_SMDBA_._CATALOG_'.
DBCC results for '_SMDBA_.TCSHIPADDR'.
There are 6 rows in 2 pages for object '_SMDBA_.TCSHIPADDR'.
DBCC results for 'SMSYSBASEVIEWDATA'.
There are 2185 rows in 28 pages for object 'SMSYSBASEVIEWDATA'.
DBCC results for 'SMSYSCI'.
There are 0 rows in 1 pages for object 'SMSYSCI'.
DBCC results for 'SMSYSCRFORMS'.
There are 95 rows in 2 pages for object 'SMSYSCRFORMS'.
DBCC results for 'SMSYSEMAILFORUMLOG'.
There are 0 rows in 0 pages for object 'SMSYSEMAILFORUMLOG'.
DBCC results for 'NAMSYSPROPERTIES'.
There are 44 rows in 1 pages for object 'NAMSYSPROPERTIES'.
DBCC results for 'SMSYSEMAILFORUMS'.
There are 7 rows in 1 pages for object 'SMSYSEMAILFORUMS'.
DBCC results for 'NAMSYSSERVERS'.
There are 8 rows in 1 pages for object 'NAMSYSSERVERS'.
DBCC results for '_SMDBA_.CMSDEPTCODES'.
There are 28 rows in 1 pages for object '_SMDBA_.CMSDEPTCODES'.
DBCC results for 'SMSYSEXTHELP'.
There are 0 rows in 0 pages for object 'SMSYSEXTHELP'.
DBCC results for 'SMSYSFKDATA'.
There are 320 rows in 8 pages for object 'SMSYSFKDATA'.
DBCC results for 'SMSYSFLAGS'.
There are 27 rows in 1 pages for object 'SMSYSFLAGS'.
DBCC results for 'SMSYSFORMDATA'.
There are 487 rows in 5 pages for object 'SMSYSFORMDATA'.
DBCC results for 'SMSYSFORMAGR'.
There are 0 rows in 0 pages for object 'SMSYSFORMAGR'.
DBCC results for 'SMSYSFORMSETS'.
There are 2 rows in 1 pages for object 'SMSYSFORMSETS'.
DBCC results for '_SMDBA_.TCBILLADDR'.
There are 2 rows in 1 pages for object '_SMDBA_.TCBILLADDR'.
DBCC results for 'SMSYSHOTNEWS'.
There are 0 rows in 0 pages for object 'SMSYSHOTNEWS'.
DBCC results for 'dtproperties'.
There are 7 rows in 1 pages for object 'dtproperties'.
DBCC results for 'SMSYSIDXHELPER'.
There are 16 rows in 1 pages for object 'SMSYSIDXHELPER'.
DBCC results for 'SMSYSKBIDATA'.
There are 0 rows in 0 pages for object 'SMSYSKBIDATA'.
DBCC results for 'SMSYSKBIDELLOG'.
There are 0 rows in 0 pages for object 'SMSYSKBIDELLOG'.
DBCC results for 'SMSYSLASTMODIFIED'.
There are 1 rows in 1 pages for object 'SMSYSLASTMODIFIED'.
DBCC results for 'SMSYSLEARNLET'.
There are 0 rows in 0 pages for object 'SMSYSLEARNLET'.
DBCC results for '_SMDBA_.CMSPERSNLTYP'.
There are 26 rows in 1 pages for object '_SMDBA_.CMSPERSNLTYP'.
DBCC results for 'SMSYSLI'.
There are 0 rows in 0 pages for object 'SMSYSLI'.
DBCC results for 'SMSYSLOCKINFO'.
There are 0 rows in 0 pages for object 'SMSYSLOCKINFO'.
DBCC results for 'SMSYSLU'.
There are 0 rows in 0 pages for object 'SMSYSLU'.
DBCC results for '_SMDBA_._INVSUBCAT_'.
There are 0 rows in 0 pages for object '_SMDBA_._INVSUBCAT_'.
DBCC results for 'SMSYSMAIL'.
There are 0 rows in 0 pages for object 'SMSYSMAIL'.
DBCC results for 'SMSYSMTREE'.
There are 0 rows in 0 pages for object 'SMSYSMTREE'.
DBCC results for '_SMDBA_._TELMASTE_'.
There are 65528 rows in 2533 pages for object '_SMDBA_._TELMASTE_'.
DBCC results for 'SMSYSPATHS'.
There are 0 rows in 0 pages for object 'SMSYSPATHS'.
DBCC results for 'SMSYSPERMSHELPER'.
There are 4 rows in 1 pages for object 'SMSYSPERMSHELPER'.
DBCC results for 'SMSYSPROCESS'.
There are 5 rows in 1 pages for object 'SMSYSPROCESS'.
DBCC results for 'SMSYSQUERY'.
There are 79 rows in 1 pages for object 'SMSYSQUERY'.
DBCC results for 'SMSYSQUERYCONDITIONS'.
There are 114 rows in 1 pages for object 'SMSYSQUERYCONDITIONS'.
DBCC results for 'SMSYSQUERYFIELDS'.
There are 2647 rows in 8 pages for object 'SMSYSQUERYFIELDS'.
DBCC results for 'SMSYSQUERYSORT'.
There are 49 rows in 1 pages for object 'SMSYSQUERYSORT'.
DBCC results for 'SMSYSRECNUM'.
There are 216 rows in 2 pages for object 'SMSYSRECNUM'.
DBCC results for 'NAMSYSPPMAINPAGE'.
There are 35 rows in 1 pages for object 'NAMSYSPPMAINPAGE'.
DBCC results for 'SMSYSSETUPDATA'.
There are 8 rows in 1 pages for object 'SMSYSSETUPDATA'.
DBCC results for 'NAMSYSPPDETAILPAGE'.
There are 11 rows in 1 pages for object 'NAMSYSPPDETAILPAGE'.
DBCC results for 'NAMSYSSEARCHGROUP'.
There are 0 rows in 1 pages for object 'NAMSYSSEARCHGROUP'.
DBCC results for 'SMSYSSIRDELLOG'.
There are 334 rows in 8 pages for object 'SMSYSSIRDELLOG'.
DBCC results for '_SMDBA_.SUBCATEGORY'.
There are 121 rows in 3 pages for object '_SMDBA_.SUBCATEGORY'.
DBCC results for 'NAMSYSSEARCHFIELDS'.
There are 0 rows in 1 pages for object 'NAMSYSSEARCHFIELDS'.
DBCC results for 'SMSYSSTATUS'.
There are 0 rows in 1 pages for object 'SMSYSSTATUS'.
DBCC results for '_SMDBA_.TCCOACATEG'.
There are 17 rows in 1 pages for object '_SMDBA_.TCCOACATEG'.
DBCC results for 'NAMSYSCSLANGUAGE'.
There are 5 rows in 1 pages for object 'NAMSYSCSLANGUAGE'.
DBCC results for 'SMSYSSTOPWATCH'.
There are 0 rows in 0 pages for object 'SMSYSSTOPWATCH'.
DBCC results for 'NAMSYSCSFORMS'.
There are 15 rows in 1 pages for object 'NAMSYSCSFORMS'.
DBCC results for 'SMSYSTABLES'.
There are 86 rows in 1 pages for object 'SMSYSTABLES'.
DBCC results for 'NAMSYSCSLANGUAGEFORMS'.
There are 71 rows in 2 pages for object 'NAMSYSCSLANGUAGEFORMS'.
DBCC results for 'SMSYSTAGS'.
There are 0 rows in 1 pages for object 'SMSYSTAGS'.
DBCC results for 'NAMSYSCSNAVIGATORS'.
There are 3 rows in 1 pages for object 'NAMSYSCSNAVIGATORS'.
DBCC results for 'SMSYSTEMPLATES'.
There are 6 rows in 1 pages for object 'SMSYSTEMPLATES'.
DBCC results for 'NAMSYSCSLANGNAVIGATORS'.
There are 7 rows in 1 pages for object 'NAMSYSCSLANGNAVIGATORS'.
DBCC results for 'SMSYSUSERDATA'.
There are 78 rows in 1 pages for object 'SMSYSUSERDATA'.
DBCC results for 'NAMSYSCSPOPUPS'.
There are 58 rows in 1 pages for object 'NAMSYSCSPOPUPS'.
DBCC results for 'SMSYSVIEWS'.
There are 2236 rows in 35 pages for object 'SMSYSVIEWS'.
DBCC results for 'NAMSYSCSLANGPOPUPS'.
There are 231 rows in 5 pages for object 'NAMSYSCSLANGPOPUPS'.
DBCC results for 'SMSYSWID'.
There are 28 rows in 1 pages for object 'SMSYSWID'.
DBCC results for 'NAMSYSCSCONFIG'.
There are 1 rows in 1 pages for object 'NAMSYSCSCONFIG'.
DBCC results for 'SMUSERFLAGS'.
There are 306 rows in 4 pages for object 'SMUSERFLAGS'.
DBCC results for 'NAMSYSCSUIASSIGNS'.
There are 0 rows in 1 pages for object 'NAMSYSCSUIASSIGNS'.
DBCC results for '_SMDBA_._ACTIONS_'.
There are 85 rows in 4 pages for object '_SMDBA_._ACTIONS_'.
DBCC results for 'NAMXSL'.
There are 0 rows in 1 pages for object 'NAMXSL'.
DBCC results for '_SMDBA_._AUTHOR_'.
There are 13 rows in 2 pages for object '_SMDBA_._AUTHOR_'.
DBCC results for 'NAMXSLALTLABELS'.
There are 0 rows in 1 pages for object 'NAMXSLALTLABELS'.
DBCC results for 'NAMXSLASSIGN'.
There are 0 rows in 1 pages for object 'NAMXSLASSIGN'.
DBCC results for '_SMDBA_._CATEGORY_'.
There are 15 rows in 1 pages for object '_SMDBA_._CATEGORY_'.
CHECKDB found 0 allocation errors and 6 consistency errors in table '_SMDBA_._CATEGORY_' (object ID 1413580074).
DBCC results for 'NAMSYSCSDTCONFIG'.
There are 5 rows in 1 pages for object 'NAMSYSCSDTCONFIG'.
DBCC results for '_SMDBA_._COMPANY_'.
There are 0 rows in 1 pages for object '_SMDBA_._COMPANY_'.
DBCC results for '_SMDBA_._FAQ_'.
There are 0 rows in 1 pages for object '_SMDBA_._FAQ_'.
DBCC results for '_SMDBA_.MANUFACTURER'.
There are 84 rows in 4 pages for object '_SMDBA_.MANUFACTURER'.
DBCC results for 'NAMCHATQUEUE'.
There are 0 rows in 1 pages for object 'NAMCHATQUEUE'.
DBCC results for '_SMDBA_._CONFIGDET_'.
There are 3 rows in 1 pages for object '_SMDBA_._CONFIGDET_'.
DBCC results for 'NAMSYSCSFOLDERS'.
There are 997 rows in 10 pages for object 'NAMSYSCSFOLDERS'.
DBCC results for '_SMDBA_._CONFIG_'.
There are 3 rows in 2 pages for object '_SMDBA_._CONFIG_'.
DBCC results for 'NAMSYSCSLOGINHTML'.
There are 11 rows in 1 pages for object 'NAMSYSCSLOGINHTML'.
DBCC results for 'NAMSYSHHASSIGNS'.
There are 0 rows in 1 pages for object 'NAMSYSHHASSIGNS'.
DBCC results for '_SMDBA_._CUSTOBS_'.
There are 0 rows in 1 pages for object '_SMDBA_._CUSTOBS_'.
DBCC results for 'NAMSYSHHFIELDS'.
There are 0 rows in 1 pages for object 'NAMSYSHHFIELDS'.
DBCC results for '_SMDBA_._CUSTOMER_'.
There are 2084 rows in 100 pages for object '_SMDBA_._CUSTOMER_'.
CHECKDB found 27 allocation errors and 10 consistency errors in table '_SMDBA_._CUSTOMER_' (object ID 1509580416).
DBCC results for 'NAMSYSHHFILTERS'.
There are 0 rows in 1 pages for object 'NAMSYSHHFILTERS'.
DBCC results for '_SMDBA_._DEPART_'.
There are 0 rows in 1 pages for object '_SMDBA_._DEPART_'.
DBCC results for 'NAMSYSHHFORMS'.
There are 0 rows in 1 pages for object 'NAMSYSHHFORMS'.
DBCC results for '_SMDBA_._GMT_'.
There are 51 rows in 1 pages for object '_SMDBA_._GMT_'.
DBCC results for 'NAMSYSHHNAVFORMS'.
There are 0 rows in 1 pages for object 'NAMSYSHHNAVFORMS'.
DBCC results for '_SMDBA_._GROUPDET_'.
There are 103 rows in 4 pages for object '_SMDBA_._GROUPDET_'.
DBCC results for '_SMDBA_._CONTRACT_'.
There are 4 rows in 1 pages for object '_SMDBA_._CONTRACT_'.
DBCC results for 'NAMSYSHHNAVS'.
There are 0 rows in 1 pages for object 'NAMSYSHHNAVS'.
DBCC results for '_SMDBA_._GROUPS_'.
There are 25 rows in 3 pages for object '_SMDBA_._GROUPS_'.
DBCC results for 'NAMSYSHHSYNCLOG'.
There are 0 rows in 1 pages for object 'NAMSYSHHSYNCLOG'.
DBCC results for '_SMDBA_._INVACTIONS_'.
There are 6 rows in 1 pages for object '_SMDBA_._INVACTIONS_'.
DBCC results for 'NAMSYSHHUSERFIELDEXCLUSIONS'.
There are 0 rows in 1 pages for object 'NAMSYSHHUSERFIELDEXCLUSIONS'.
DBCC results for '_SMDBA_._INVENTOR_'.
There are 2 rows in 1 pages for object '_SMDBA_._INVENTOR_'.
DBCC results for 'Results'.
There are 6 rows in 1 pages for object 'Results'.
DBCC results for 'NAMSYSHHUSERFILTERPREFS'.
There are 0 rows in 1 pages for object 'NAMSYSHHUSERFILTERPREFS'.
DBCC results for '_SMDBA_._INVSRVHIST_'.
There are 0 rows in 1 pages for object '_SMDBA_._INVSRVHIST_'.
DBCC results for 'NAMSYSHHFILTERSDETAIL'.
There are 0 rows in 0 pages for object 'NAMSYSHHFILTERSDETAIL'.
DBCC results for 'NAMSYSHHPOPUPS'.
There are 0 rows in 0 pages for object 'NAMSYSHHPOPUPS'.
DBCC results for '_SMDBA_._PERSONNEL_'.
There are 78 rows in 2 pages for object '_SMDBA_._PERSONNEL_'.
DBCC results for '_SMDBA_.PAYMNTMETHOD'.
There are 3 rows in 1 pages for object '_SMDBA_.PAYMNTMETHOD'.
DBCC results for 'NAMSYSSUBREPORT'.
There are 12 rows in 1 pages for object 'NAMSYSSUBREPORT'.
DBCC results for 'NAMSYSHHACTIONS'.
There are 0 rows in 0 pages for object 'NAMSYSHHACTIONS'.
DBCC results for 'NAMSYSSUBRPTDETAILS'.
There are 3 rows in 1 pages for object 'NAMSYSSUBRPTDETAILS'.
DBCC results for '_SMDBA_._ATTACH_'.
There are 163 rows in 4 pages for object '_SMDBA_._ATTACH_'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '_SMDBA_._ATTACH_' (object ID 1694681135).
DBCC results for '_SMDBA_._PURCHACT_'.
There are 23 rows in 2 pages for object '_SMDBA_._PURCHACT_'.
CHECKDB found 0 allocation errors and 5 consistency errors in table '_SMDBA_._PURCHACT_' (object ID 1701581100).
DBCC results for '_SMDBA_._CHANGEAPPR_'.
There are 60 rows in 2 pages for object '_SMDBA_._CHANGEAPPR_'.
DBCC results for '_SMDBA_._PURCHHIST_'.
There are 100 rows in 7 pages for object '_SMDBA_._PURCHHIST_'.
DBCC results for '_SMDBA_._CHANGEASMT_'.
There are 7 rows in 2 pages for object '_SMDBA_._CHANGEASMT_'.
DBCC results for '_SMDBA_._PURCHSTAT_'.
There are 11 rows in 2 pages for object '_SMDBA_._PURCHSTAT_'.
DBCC results for '_SMDBA_._CHANGEDET_'.
There are 5593 rows in 85 pages for object '_SMDBA_._CHANGEDET_'.
DBCC results for '_SMDBA_.SCSTATUS'.
There are 12 rows in 2 pages for object '_SMDBA_.SCSTATUS'.
DBCC results for '_SMDBA_._RECURRING_'.
There are 8 rows in 2 pages for object '_SMDBA_._RECURRING_'.
DBCC results for '_SMDBA_._CHANGE_'.
There are 1241 rows in 47 pages for object '_SMDBA_._CHANGE_'.
DBCC results for '_SMDBA_._LICEXCEED_'.
There are 1369 rows in 36 pages for object '_SMDBA_._LICEXCEED_'.
DBCC results for '_SMDBA_._SLA_'.
There are 0 rows in 1 pages for object '_SMDBA_._SLA_'.
DBCC results for '_SMDBA_._CHGPMLINKS_'.
There are 0 rows in 1 pages for object '_SMDBA_._CHGPMLINKS_'.
DBCC results for '_SMDBA_._SLA_DEFLT_'.
There are 0 rows in 1 pages for object '_SMDBA_._SLA_DEFLT_'.
DBCC results for '_SMDBA_._CICHGPMLNK_'.
There are 0 rows in 1 pages for object '_SMDBA_._CICHGPMLNK_'.
DBCC results for '_SMDBA_._STDCFGDET_'.
There are 0 rows in 1 pages for object '_SMDBA_._STDCFGDET_'.
DBCC results for '_SMDBA_._CMSTATUS_'.
There are 8 rows in 2 pages for object '_SMDBA_._CMSTATUS_'.
DBCC results for '_SMDBA_._STDCFG_'.
There are 1 rows in 1 pages for object '_SMDBA_._STDCFG_'.
DBCC results for '_SMDBA_._CONFIGREL_'.
There are 0 rows in 1 pages for object '_SMDBA_._CONFIGREL_'.
DBCC results for '_SMDBA_._STDDESCR_'.
There are 916 rows in 11 pages for object '_SMDBA_._STDDESCR_'.
DBCC results for '_SMDBA_._PROBMGMT_'.
There are 2 rows in 1 pages for object '_SMDBA_._PROBMGMT_'.
DBCC results for '_SMDBA_._STDRESOL_'.
There are 917 rows in 13 pages for object '_SMDBA_._STDRESOL_'.
DBCC results for '_SMDBA_._SUBJECTS_'.
There are 253 rows in 8 pages for object '_SMDBA_._SUBJECTS_'.
DBCC results for '_SMDBA_.TCINITEMSTAT'.
There are 4 rows in 1 pages for object '_SMDBA_.TCINITEMSTAT'.
DBCC results for '_SMDBA_._SUBJTYPES_'.
There are 36 rows in 2 pages for object '_SMDBA_._SUBJTYPES_'.
DBCC results for '_SMDBA_._TELATTACH_'.
There are 193 rows in 7 pages for object '_SMDBA_._TELATTACH_'.
DBCC results for '_SMDBA_.TCCHARTOFACT'.
There are 205 rows in 3 pages for object '_SMDBA_.TCCHARTOFACT'.
DBCC results for 'NAMSYSCSBRRULES'.
There are 78 rows in 3 pages for object 'NAMSYSCSBRRULES'.
DBCC results for '_SMDBA_._IMPACT_'.
There are 3 rows in 1 pages for object '_SMDBA_._IMPACT_'.
DBCC results for '_SMDBA_._TELDETAI_'.
There are 320568 rows in 3961 pages for object '_SMDBA_._TELDETAI_'.
DBCC results for 'NAMSYSCSBRCONDITIONS'.
There are 159 rows in 2 pages for object 'NAMSYSCSBRCONDITIONS'.
DBCC results for '_SMDBA_._PRIORITY_'.
There are 0 rows in 1 pages for object '_SMDBA_._PRIORITY_'.
DBCC results for 'NAMSYSCSBRACTIONS'.
There are 119 rows in 1 pages for object 'NAMSYSCSBRACTIONS'.
DBCC results for '_SMDBA_._PMDET_'.
There are 2 rows in 1 pages for object '_SMDBA_._PMDET_'.
DBCC results for 'MAGIC.Copy_CUSTOMER_'.
There are 1685 rows in 66 pages for object 'MAGIC.Copy_CUSTOMER_'.
DBCC results for 'NAMSYSCSBRASSIGNS'.
There are 86 rows in 1 pages for object 'NAMSYSCSBRASSIGNS'.
DBCC results for 'NAMSYSWORK'.
There are 1 rows in 1 pages for object 'NAMSYSWORK'.
DBCC results for '_SMDBA_._WBACTIONOT_'.
There are 188 rows in 8 pages for object '_SMDBA_._WBACTIONOT_'.
DBCC results for 'NAMSYSCSBRSCRIPTS'.
There are 17 rows in 1 pages for object 'NAMSYSCSBRSCRIPTS'.
DBCC results for '_SMDBA_._INVENTOREL_'.
There are 0 rows in 1 pages for object '_SMDBA_._INVENTOREL_'.
DBCC results for '_SMDBA_._WHITEBOARD_'.
There are 53 rows in 2 pages for object '_SMDBA_._WHITEBOARD_'.
DBCC results for 'NAMSYSCLIENTINFO'.
There are 0 rows in 1 pages for object 'NAMSYSCLIENTINFO'.
DBCC results for '_SMDBA_._WORKDET_'.
There are 386 rows in 11 pages for object '_SMDBA_._WORKDET_'.
DBCC results for 'NAMLOCKCONFIG'.
There are 86 rows in 1 pages for object 'NAMLOCKCONFIG'.
DBCC results for '_SMDBA_.SCHISTORY'.
There are 2 rows in 1 pages for object '_SMDBA_.SCHISTORY'.
DBCC results for '_SMDBA_._WORKORD_'.
There are 74 rows in 5 pages for object '_SMDBA_._WORKORD_'.
DBCC results for '_SMDBA_._MAILLISTEN_'.
There are 0 rows in 8 pages for object '_SMDBA_._MAILLISTEN_'.
DBCC results for 'NAMSYSPROTECTS'.
There are 65452 rows in 169 pages for object 'NAMSYSPROTECTS'.
DBCC results for 'NAMSYS_SAVE_PERMS'.
There are 7 rows in 1 pages for object 'NAMSYS_SAVE_PERMS'.
DBCC results for 'NAMSYS_SEG_LIST'.
There are 2 rows in 1 pages for object 'NAMSYS_SEG_LIST'.
DBCC results for 'NAMSYSCTIEVENTTYPES'.
There are 0 rows in 1 pages for object 'NAMSYSCTIEVENTTYPES'.
DBCC results for 'NAMSYSCTICONFIGS'.
There are 0 rows in 1 pages for object 'NAMSYSCTICONFIGS'.
DBCC results for 'NAMSYSMETASYNCQUEUE'.
There are 180 rows in 2 pages for object 'NAMSYSMETASYNCQUEUE'.
DBCC results for 'NAMSYSCTIPREPOPCOLS'.
There are 0 rows in 1 pages for object 'NAMSYSCTIPREPOPCOLS'.
DBCC results for 'NAMSYSCTISEARCHPATHS'.
There are 0 rows in 1 pages for object 'NAMSYSCTISEARCHPATHS'.
CHECKDB found 27 allocation errors and 22 consistency errors in database 'Magic1'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Magic1 ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.



coolerbob
Aged Yak Warrior

United Kingdom
841 Posts

Posted - 08/01/2005 :  12:18:24  Show Profile  Reply with Quote
So did you do what the error message said and run: "DBCC CHECKDB repair_allow_data_loss" ?
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 08/01/2005 :  12:21:41  Show Profile  Visit paulrandal's Homepage  Reply with Quote
Hi Ron,

The original errors mean that several IAM chains comprising non-clustered indexes do not have metadata in the system tables (that's the special meaning of parent page (0:0) in this case).

By running repair using CHECKALLOC, you've only corrected some of the errors. The repair for 2576 is to try to rebuild (or remove) the broken IAM chain, but its necessary to also deallocate any pages that those IAM pages referenced, hence all the residual errors that are still left. You should have run repair using CHECKDB. Doing that now should hopefully clear up all the errors and rebuild the non-clustered indexes that are affected.

Do you have the output from the CHECKALLOC repair you ran?

Note that you shouldn't have lost any data here as its only non-clustered indexes that are corrupt.

Now, two more things:

1) I strongly advise not running repair if at all possible. The REPAIR_ALLOW_DATA_LOSS option is deliberately named that because it usually requires deleting data to obtain structural consistency of the database. Its far better to try to understand what the errors mean and the consequences of running repair are. The latest BOL update has full information for all errors that CHECKDB returns, including what repair will do. You should also strive to work out why these errors occured.

Do any of the tables referenced in the original set of errors meet the following conditions?
- a table includes a computed column
- the table has a primary key column that is also referenced by another nonclustered index
- there is an indexed view that references the table
- the table is reindexed (e.g. via DBCC DBREINDEX)

If so, then the 2576s are a known problem that is fixed in SP4 and the latest SP3 QFE.

If not, did anyone try to drop these non-clustered indexes by manually updating sysindexes? This is a common cause of these errors.

2) Running repair should be the last thing tried to recover from errors. Its always better to recover using up-to-date backups and/or extracting as much data as possible before running repair/restoring.

Thanks

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

RonM
Starting Member

8 Posts

Posted - 08/01/2005 :  12:47:03  Show Profile  Reply with Quote
Paul

First I have not ran anything on our production databases. The DBCC CHECKALLOC (magic1, repair_allow_data_loss) was ran a copy of the database.

Since the DBCC CHECKALLOC (magic1, repair_allow_data_loss) did not fix the problem, can you tell me the line need to run? I will start on a fresh copy of the database.

The result of my DBCC CHECKALLOC (magic1, repair_allow_data_loss) is below. (some of the " Object ID 1, Index ID 3, index extents 4, pages 22, mixed extent pages 9." lines were removed to make the size manageable). If I run it a second time it will get the errors down to 27.

thanks
Total number of extents = 6348, used pages = 48123, reserved pages = 50737 in this database.
(number of mixed extents = 319, mixed pages = 2505) in this database.
CHECKALLOC found 60 allocation errors and 0 consistency errors in database 'Magic22'.
CHECKALLOC fixed 60 allocation errors and 0 consistency errors in database 'Magic22'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.


Edited by - RonM on 08/01/2005 13:39:43
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 08/01/2005 :  13:08:10  Show Profile  Visit paulrandal's Homepage  Reply with Quote
Ron,

Can you take a fresh copy of the prod db and run the following on it (and then post the results):

DBCC CHECKDB (dbname) WITH NO_INFOMSGS, ALL_ERRORMSGS

This will let us see everything wrong with the db without all the extra info clutter.

Thanks

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

RonM
Starting Member

8 Posts

Posted - 08/01/2005 :  13:34:47  Show Profile  Reply with Quote
Paul

I did as you requested, restored fresh copy. The results of the query ar eposted below:

thanks again

Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:3231) object ID 1397580017 index ID 24 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:3491) object ID 1397580017 index ID 25 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10852) object ID 1397580017 index ID 26 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10864) object ID 1397580017 index ID 30 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:25006) object ID 1413580074 index ID 2 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1413580074, index ID 2 contain allocations for the same interval. IAM pages (1:25006) and (1:29873).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:12708) object ID 1413580074 index ID 7 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1413580074, index ID 7 contain allocations for the same interval. IAM pages (1:12708) and (1:31137).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10122) object ID 1413580074 index ID 8 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1413580074, index ID 8 contain allocations for the same interval. IAM pages (1:10122) and (1:31488).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10855) object ID 1413580074 index ID 9 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:21035) object ID 1413580074 index ID 9 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1413580074, index ID 9 contain allocations for the same interval. IAM pages (1:10855) and (1:31492).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1413580074, index ID 9 contain allocations for the same interval. IAM pages (1:21035) and (1:31492).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:45956) object ID 1413580074 index ID 11 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1413580074, index ID 11 contain allocations for the same interval. IAM pages (1:45956) and (1:31497).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10862) object ID 1477580302 index ID 14 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:41778) object ID 1477580302 index ID 14 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1477580302, index ID 14 contain allocations for the same interval. IAM pages (1:10862) and (1:41778).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10867) object ID 1509580416 index ID 56 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1509580416, index ID 56 contain allocations for the same interval. IAM pages (1:10867) and (1:49193).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:11718) object ID 1509580416 index ID 57 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1509580416, index ID 57 contain allocations for the same interval. IAM pages (1:11718) and (1:49201).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:12394) object ID 1509580416 index ID 58 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1509580416, index ID 58 contain allocations for the same interval. IAM pages (1:12394) and (1:49217).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10121) object ID 1509580416 index ID 62 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1509580416, index ID 62 contain allocations for the same interval. IAM pages (1:10121) and (1:49468).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:18982) object ID 1605580758 index ID 28 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:23818) object ID 1605580758 index ID 29 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:31140) object ID 1669580986 index ID 18 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:31142) object ID 1669580986 index ID 19 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:31360) object ID 1669580986 index ID 20 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:31364) object ID 1669580986 index ID 21 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:31367) object ID 1669580986 index ID 22 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:40006) object ID 1669580986 index ID 23 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:40136) object ID 1669580986 index ID 24 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:12704) object ID 1669580986 index ID 30 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:13528) object ID 1669580986 index ID 31 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:23822) object ID 1685581043 index ID 25 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:23848) object ID 1685581043 index ID 26 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:23851) object ID 1685581043 index ID 27 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:23854) object ID 1685581043 index ID 28 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:26869) object ID 1685581043 index ID 29 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10125) object ID 1685581043 index ID 35 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:11179) object ID 1685581043 index ID 36 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:12711) object ID 1694681135 index ID 13 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1694681135, index ID 13 contain allocations for the same interval. IAM pages (1:12711) and (1:49034).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:11183) object ID 1701581100 index ID 2 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1701581100, index ID 2 contain allocations for the same interval. IAM pages (1:11183) and (1:1239).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:11182) object ID 1701581100 index ID 7 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1701581100, index ID 7 contain allocations for the same interval. IAM pages (1:11182) and (1:9660).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:11181) object ID 1701581100 index ID 8 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1701581100, index ID 8 contain allocations for the same interval. IAM pages (1:11181) and (1:9662).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:11180) object ID 1701581100 index ID 9 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1701581100, index ID 9 contain allocations for the same interval. IAM pages (1:11180) and (1:9952).
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object ID 1397580017)' (object ID 1397580017).
CHECKDB found 12 allocation errors and 0 consistency errors in table '_SMDBA_._CATEGORY_' (object ID 1413580074).
CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 1477580302)' (object ID 1477580302).
CHECKDB found 8 allocation errors and 0 consistency errors in table '_SMDBA_._CUSTOMER_' (object ID 1509580416).
CHECKDB found 2 allocation errors and 0 consistency errors in table '_SMDBA_._INVENTOR_' (object ID 1605580758).
CHECKDB found 9 allocation errors and 0 consistency errors in table '(Object ID 1669580986)' (object ID 1669580986).
CHECKDB found 7 allocation errors and 0 consistency errors in table '(Object ID 1685581043)' (object ID 1685581043).
CHECKDB found 2 allocation errors and 0 consistency errors in table '_SMDBA_._ATTACH_' (object ID 1694681135).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:12706) object ID 1701581100 index ID 10 but was not detected in the scan.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1701581100, index ID 10 contain allocations for the same interval. IAM pages (1:12706) and (1:25277).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:45810) object ID 1733581214 index ID 7 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:45812) object ID 1733581214 index ID 8 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:10127) object ID 1941581955 index ID 45 but was not detected in the scan.
CHECKDB found 10 allocation errors and 0 consistency errors in table '_SMDBA_._PURCHACT_' (object ID 1701581100).
CHECKDB found 2 allocation errors and 0 consistency errors in table '_SMDBA_._PURCHSTAT_' (object ID 1733581214).
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 1941581955)' (object ID 1941581955).
CHECKDB found 60 allocation errors and 0 consistency errors in database 'Magic22'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Magic22 ).
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 08/01/2005 :  14:04:03  Show Profile  Visit paulrandal's Homepage  Reply with Quote
ok - this is nasty. What you've got is a bunch of non-clustered indexes with two IAM chains mapping the same set of pages. For each index, one IAM chain is correctly linked into sysindexes and the other is not. You'll notice that the pages referenced in the 2576 errors also appear in 8947 errors.

Do any of the conditions described in http://support.microsoft.com/kb/816084 apply?

I've never seen this caused by h/w problems - if its not the problem in the KB article above (quite rare) then its always from someone dropping indexes manually. Has anyone done this?

Thanks

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

RonM
Starting Member

8 Posts

Posted - 08/01/2005 :  15:20:43  Show Profile  Reply with Quote
Paul

I have determined that for some reason this did not get caught quickly and this condition has been present for some time but the database is operating well and without problems. Considering this I have no good backup. This also makes determing the cause a little more difficult.

In response to your 2 questions. Yes indexes could have been dropped manually. In regard to Bug #: 364183, some of those conditions apply as well. But I would say the cause is probably a result from dropping indexes.

Please tell me how to repair.

thank you
Ron
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 08/01/2005 :  16:11:19  Show Profile  Visit paulrandal's Homepage  Reply with Quote
quote:
Originally posted by RonM

Paul

I have determined that for some reason this did not get caught quickly and this condition has been present for some time but the database is operating well and without problems. Considering this I have no good backup. This also makes determing the cause a little more difficult.

In response to your 2 questions. Yes indexes could have been dropped manually. In regard to Bug #: 364183, some of those conditions apply as well. But I would say the cause is probably a result from dropping indexes.

Please tell me how to repair.

thank you
Ron



This is good (that the problem is not likely h/w or a bug). You should impress upon your DBAs the dangers of messing about with the system tables - it usually leads to problems.

You have two choices:

1) assuming you have the index definitions on hand:
a) drop all non-clustered indexes on the tables with corruption
b) run DBCC CHECKDB (MAGIC, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS
c) recreate all the non-clustered indexes

2) if you don't have the index definitions available:
a) run DBCC CHECKDB (MAGIC, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS
b) run DBCC CHECKDB (MAGIC) WITH NO_INFOMSGS
c) repeat steps a) and b) until no more errors are reported

In option 2, repeatedly running repair is necessary because repairing these errors usually leads to other errors becoming apparent (i.e. the IAM page errors cause some deeper processing to be skipped - so fixing them allows further processing and more errors can be reported). Rest assured that these all are in the non-clustered indexes though.

My recommendation is to do option 1 if possible, and to make sure it works on the db copy before running on the prod database.

Let me know how you get on.

Thanks

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

RonM
Starting Member

8 Posts

Posted - 08/01/2005 :  16:14:58  Show Profile  Reply with Quote
Paul

Do you think running either option 1 or 2 will cause data loss?

thanks again
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 08/01/2005 :  16:19:53  Show Profile  Visit paulrandal's Homepage  Reply with Quote
quote:
Originally posted by RonM

Paul

Do you think running either option 1 or 2 will cause data loss?

thanks again



No - not given the errors you've posted. They're all in non-clustered indexes which are redundant copies of parts of the table.

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

Kristen
Test

United Kingdom
22431 Posts

Posted - 08/02/2005 :  00:47:31  Show Profile  Reply with Quote
Sorry to butt in here, but I am chuckling at one of the parameters to DBCC CHECKDB being "MAGIC" - I'm sure that's how Paul envisages his baby

Kristen
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 08/02/2005 :  12:06:39  Show Profile  Visit paulrandal's Homepage  Reply with Quote
quote:
Originally posted by Kristen

Sorry to butt in here, but I am chuckling at one of the parameters to DBCC CHECKDB being "MAGIC" - I'm sure that's how Paul envisages his baby

Kristen



That's one of the undocumented options

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

bell27
Starting Member

4 Posts

Posted - 08/23/2005 :  11:02:39  Show Profile  Visit bell27's Homepage  Reply with Quote
How will i know hen it is done?

<edit> spam links removed </edit>
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 08/25/2005 :  15:19:25  Show Profile  Visit paulrandal's Homepage  Reply with Quote
When what is done exactly?

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

gkoplitz
Starting Member

USA
1 Posts

Posted - 01/07/2010 :  10:49:18  Show Profile  Reply with Quote
Was there a resolution to this issue with step 1 or 2?

Edited by - gkoplitz on 01/07/2010 11:09:32
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 01/08/2010 :  03:21:42  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Err, 5 year old post. Do you have a new question? If so, can you start a new thread please?

--
Gail Shaw
SQL Server MVP
Go to Top of Page

GURUNADHA7111
Starting Member

India
2 Posts

Posted - 06/10/2010 :  18:08:59  Show Profile  Reply with Quote
This is the error i ma getting can any one help me.

Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (1:5673177) is pointed to by the previous pointer of IAM page (1:5442285) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057598451253248 (type Unknown), but it was not detected in the scan.



DBAGuru,India
http://www.acslimited.com/webIndia/index.html

Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 06/11/2010 :  03:12:11  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Please post your question in a new thread. Thank you.

--
Gail Shaw
SQL Server MVP
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.64 seconds. Powered By: Snitz Forums 2000