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.
| Author |
Topic |
|
ashgray
Starting Member
4 Posts |
 Posted - 2005-08-31 : 12:33:24
|
| DBCC results for 'DocCollections'.DBCC results for 'sysobjects'.There are 116 rows in 4 pages for object 'sysobjects'.DBCC results for 'sysindexes'.There are 148 rows in 7 pages for object 'sysindexes'.DBCC results for 'syscolumns'.There are 666 rows in 12 pages for object 'syscolumns'.DBCC results for 'systypes'.There are 26 rows in 1 pages for object 'systypes'.DBCC results for 'syscomments'.There are 157 rows in 15 pages for object 'syscomments'.DBCC results for 'sysfiles1'.There are 2 rows in 1 pages for object 'sysfiles1'.DBCC results for 'syspermissions'.There are 104 rows in 1 pages for object 'syspermissions'.DBCC results for 'sysusers'.There are 108 rows in 2 pages for object 'sysusers'.DBCC results for 'sysproperties'.There are 1702 rows in 26 pages for object 'sysproperties'.DBCC results for 'sysdepends'.There are 474 rows in 3 pages for object 'sysdepends'.DBCC results for 'sysreferences'.There are 2 rows in 1 pages for object 'sysreferences'.DBCC results for 'sysfulltextcatalogs'.There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.DBCC results for 'sysfulltextnotify'.There are 0 rows in 0 pages for object 'sysfulltextnotify'.DBCC results for 'sysfilegroups'.There are 1 rows in 1 pages for object 'sysfilegroups'.DBCC results for 'tblCommentsArchive'.There are 64678 rows in 395 pages for object 'tblCommentsArchive'.DBCC results for 'tblLoanConditionsDeleted'.There are 0 rows in 0 pages for object 'tblLoanConditionsDeleted'.DBCC results for 'dtproperties'.There are 7 rows in 1 pages for object 'dtproperties'.DBCC results for 'LoanInfoFix'.There are 52421 rows in 166 pages for object 'LoanInfoFix'.DBCC results for 'tblLoanConditionsFIX'.There are 392167 rows in 2099 pages for object 'tblLoanConditionsFIX'.DBCC results for 'tblLoanConditions'.There are 743281 rows in 6004 pages for object 'tblLoanConditions'.DBCC results for 'Conditions'.There are 144 rows in 2 pages for object 'Conditions'.DBCC results for 'REGIONS'.There are 51 rows in 1 pages for object 'REGIONS'.DBCC results for 'RegionsPhil'.There are 53 rows in 1 pages for object 'RegionsPhil'.DBCC results for 'DLQ'.There are 13569 rows in 34 pages for object 'DLQ'.DBCC results for 'CountyList'.Server: Msg 2511, Level 16, State 2, Line 1Table error: Object ID 2073058421, Index ID 0. Keys out of order on page (1:10386), slots 17 and 18.Server: Msg 8978, Level 16, State 1, Line 1Table error: Object ID 2073058421, index ID 1. Page (1:759) is missing a reference from previous page (1:10386). Possible chain linkage problem.Server: Msg 8935, Level 16, State 1, Line 1Table error: Object ID 2073058421, index ID 1. The previous link (1:10386) on page (1:10387) does not match the previous page (1:759) that the parent (1:10326), slot 81 expects for this page.Server: Msg 8936, Level 16, State 1, Line 1Table error: Object ID 2073058421, index ID 1. B-tree chain linkage mismatch. (1:759)->next = (1:10387), but (1:10387)->Prev = (1:10386).There are 3022 rows in 13 pages for object 'CountyList'.DBCC results for 'ContactPreference'.There are 4 rows in 1 pages for object 'ContactPreference'.DBCC results for 'Broker'.There are 21614 rows in 334 pages for object 'Broker'.DBCC results for 'Conversion Errors'.There are 2 rows in 1 pages for object 'Conversion Errors'.DBCC results for 'LoanInfo'.There are 271755 rows in 8970 pages for object 'LoanInfo'.CHECKDB found 0 allocation errors and 4 consistency errors in table 'LoanInfo' (object ID 2073058421).DBCC results for 'SettlementAgent'.There are 285013 rows in 4143 pages for object 'SettlementAgent'.DBCC results for 'statelist'.There are 51 rows in 1 pages for object 'statelist'.CHECKDB found 0 allocation errors and 4 consistency errors in database 'DocCollections'.repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (DocCollections ).DBCC execution completed. If DBCC printed error messages, contact your system administrator. |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-08-31 : 12:40:55
|
| What version are you on?Is there any evidence of h/w problems in the SQL errorlog or Windows event log?Did you just rebuild the clustered index on this table?ThanksPaul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
 |
|
|
ashgray
Starting Member
4 Posts |
Posted - 2005-08-31 : 12:53:26
|
quote:
Originally posted by paulrandal
What version are you on?Is there any evidence of h/w problems in the SQL errorlog or Windows event log?Did you just rebuild the clustered index on this table?ThanksPaul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Any Idea from DBCC output what is causing this?The clustered index?No hardware problems have been noticed.Error: 8908, Severity: 22, State: 6Table error: Database ID 27, object ID 2073058421, index ID 0. Chain linkage mismatch. (1:10386)->next = (1:759), but (1:759)->prev = (1:10387). Shows up in the applications log.SQL 2000 sp3I am trying to rebuild the clustered index, but it keeps giving me errors.Thinking I need to rebuild the table with an id as the key; and thatthe data is corrupt. |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-09-02 : 13:07:25
|
| It looks like a bug. I don't have access to our bug database right now. You'll get the error during rebuild as its trying to use the old index to create the new one. I'll ask Ryan to check the bug db today.Can you drop the clustered index and recreate it, or will that cause your business logic to become inconsistent? If you're going to do this, I recommend dropping all non-clustered indexes first and then recreating them after recreating the clustered index (otherwise they will all be rebuilt twice - once when the clustered index is dropped, and again when its recreated).ThanksPaul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
ryanston
Microsoft SQL Server Product Team
89 Posts |
Posted - 2005-09-02 : 20:36:45
|
| I can't find anything that's directly related to the errors you're seeing, but I do agree with Paul that this is likely an index build bug. We've fixed some of these in SP4, so perhaps it would be useful to upgrade to the latest service pack?Thanks,----------------------Ryan StonecipherDeveloper, Microsoft SQL Server Storage Engine, DBCC(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
ashgray
Starting Member
4 Posts |
Posted - 2005-09-06 : 07:35:48
|
quote:
Originally posted by ryanston
I can't find anything that's directly related to the errors you're seeing, but I do agree with Paul that this is likely an index build bug. We've fixed some of these in SP4, so perhaps it would be useful to upgrade to the latest service pack?Thanks,----------------------Ryan StonecipherDeveloper, Microsoft SQL Server Storage Engine, DBCC(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Thanks! I dropped the clustered index & table and then recreated it with no data & then moved it back. The user had created an index on a varchar that had a lot of null values, so I created an autonumber and used it for the key. We'll see if this helps in the future. I am going to upgrade to SP4 soon because I have seen another bug that was suppose to be fixed in SP4.Thanks again for the help! |
|
|
|
aluocn
Starting Member
2 Posts |
Posted - 2005-09-10 : 03:51:57
|
| Has the problem been resolved now ? |
|
|
|
aluocn
Starting Member
2 Posts |
Posted - 2005-09-10 : 03:53:19
|
| I encounted a similar problem ! |
|
|
|
|
|
|
|
|
dbcc errors