Master DB Errors - SQL Server Forums

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

Master DB Errors

Author

Topic

ScottH
Starting Member

2 Posts

Posted - 2006-02-02 : 09:22:51

Recently we had a hardware failure that caused issues with our server. We restored all of the databases from backups that appeared as "suspect" and all was back up and running. The 3rd party that assisted in the recovery efforts noted a problem with the Master database and stated that they believe it is a problem that will be resolved with install of SP3. This server is SQL2000 with NO service packs applied. The error is posted below and I am just curious if someone in the know can tell by looking at it if this could be true or if there is going to be more to it.

Thanks in advance for any information.

#####################################################################
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:11) identified by (RID = (1:439:11) id = 779865845 and colid = 1 and number = 1) has index values (id = 779865845 and name = '@option_name' and number = 1 and id = 779865845 and colid = 1 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:12) identified by (RID = (1:439:12) id = 779865845 and colid = 2 and number = 1) has index values (id = 779865845 and name = '@segname' and number = 1 and id = 779865845 and colid = 2 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:13) identified by (RID = (1:439:13) id = 779865845 and colid = 3 and number = 1) has index values (id = 779865845 and name = '@objname' and number = 1 and id = 779865845 and colid = 3 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:14) identified by (RID = (1:439:14) id = 779865845 and colid = 4 and number = 1) has index values (id = 779865845 and name = '@objid' and number = 1 and id = 779865845 and colid = 4 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:15) identified by (RID = (1:439:15) id = 779865845 and colid = 5 and number = 1) has index values (id = 779865845 and name = '@line_no' and number = 1 and id = 779865845 and colid = 5 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:16) identified by (RID = (1:439:16) id = 779865845 and colid = 6 and number = 1) has index values (id = 779865845 and name = '@title' and number = 1 and id = 779865845 and colid = 6 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:34) identified by (RID = (1:439:34) id = 795865902 and colid = 1 and number = 1) has index values (id = 795865902 and name = '@option_name' and number = 1 and id = 795865902 and colid = 1 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:35) identified by (RID = (1:439:35) id = 795865902 and colid = 2 and number = 1) has index values (id = 795865902 and name = '@sproc_id' and number = 1 and id = 795865902 and colid = 2 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:36) identified by (RID = (1:439:36) id = 795865902 and colid = 3 and number = 1) has index values (id = 795865902 and name = '@log_name' and number = 1 and id = 795865902 and colid = 3 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:37) identified by (RID = (1:439:37) id = 795865902 and colid = 4 and number = 1) has index values (id = 795865902 and name = '@report_as1' and number = 1 and id = 795865902 and colid = 4 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:38) identified by (RID = (1:439:38) id = 795865902 and colid = 5 and number = 1) has index values (id = 795865902 and name = '@kpid' and number = 1 and id = 795865902 and colid = 5 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:39) identified by (RID = (1:439:39) id = 795865902 and colid = 6 and number = 1) has index values (id = 795865902 and name = '@look4bad' and number = 1 and id = 795865902 and colid = 6 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:40) identified by (RID = (1:439:40) id = 795865902 and colid = 7 and number = 1) has index values (id = 795865902 and name = '@look4block' and number = 1 and id = 795865902 and colid = 7 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:41) identified by (RID = (1:439:41) id = 795865902 and colid = 8 and number = 1) has index values (id = 795865902 and name = '@minblktime' and number = 1 and id = 795865902 and colid = 8 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:42) identified by (RID = (1:439:42) id = 795865902 and colid = 9 and number = 1) has index values (id = 795865902 and name = '@look4idle' and number = 1 and id = 795865902 and colid = 9 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:43) identified by (RID = (1:439:43) id = 795865902 and colid = 10 and number = 1) has index values (id = 795865902 and name = '@look4runaway' and number = 1 and id = 795865902 and colid = 10 and number = 1).
DBCC results for 'master'.
DBCC results for 'sysobjects'.
There are 1256 rows in 23 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 104 rows in 4 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:44) identified by (RID = (1:439:44) id = 795865902 and colid = 11 and number = 1) has index values (id = 795865902 and name = '@zero_date' and number = 1 and id = 795865902 and colid = 11 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'syscolumns' (ID 3). Missing or invalid key in index 'ncsyscolumns' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:439:45) identified by (RID = (1:439:45) id = 795865902 and colid = 12 and number = 1) has index values (id = 795865902 and name = '@column_separator' and number = 1 and id = 795865902 and colid = 12 and number = 1).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 6, index ID 0: Page (1:1115) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 6, index ID 0, page (1:1115). Test (m_freeCnt == freeCnt) failed. Values are 4866 and 8078.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 6, index ID 1. Page (1:1669) is missing a reference from previous page (1:1664). Possible chain linkage problem.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 6, index ID 1. B-tree chain linkage mismatch. (1:1664)->next = (1:1696), but (1:1696)->Prev = (1:763).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdepends' (ID 12). Missing or invalid key in index 'ncsysdepends1' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:393:187) identified by (RID = (1:393:187) deptype = 7.58884832E-321 and depid = 10 and id = 779865845 and depnumber = 1 and number = 1) has index values (id = 779865845 and number = 1 and deptype = 7.58884832E-321 and depid = 10 and depnumber = 1 and deptype = 7.58884832E-321 and depid = 10 and id = 779865845 and depnumber = 1 and number = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdepends' (ID 12). Missing or invalid key in index 'ncsysdepends1' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:393:188) identified by (RID = (1:393:188) deptype = 7.58884832E-321 and depid = 10 and id = 779865845 and depnumber = 3 and number = 1) has index values (id = 779865845 and number = 1 and deptype = 7.58884832E-321 and depid = 10 and depnumber = 3 and deptype = 7.58884832E-321 and depid = 10 and id = 779865845 and depnumber = 3 and number = 1).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'master', index 'sysdepends.ncsysdepends1' (ID 12) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:621:230) with values (id = 811865959 and number = 1 and deptype = 5.432309238E-312 and depid = 10 and depnumber = 1 and deptype = 5.432309238E-312 and depid = 10 and id = 811865959 and depnumber = 1 and number = 1) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'master', index 'sysdepends.ncsysdepends1' (ID 12) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:621:231) with values (id = 811865959 and number = 1 and deptype = 1.629692769E-311 and depid = 10 and depnumber = 3 and deptype = 1.629692769E-311 and depid = 10 and id = 811865959 and depnumber = 3 and number = 1) points to the data row identified by ().
There are 4819 rows in 86 pages for object 'syscolumns'.
CHECKDB found 0 allocation errors and 18 consistency errors in table 'syscolumns' (object ID 3).
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 1948 rows in 1250 pages for object 'syscomments'.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'syscomments' (object ID 6).
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 886 rows in 4 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 15 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 5377 rows in 26 pages for object 'sysdepends'.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'sysdepends' (object ID 12).
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysdatabases'.
There are 13 rows in 1 pages for object 'sysdatabases'.
DBCC results for 'sysxlogins'.
There are 38 rows in 1 pages for object 'sysxlogins'.
DBCC results for 'sysdevices'.
There are 6 rows in 1 pages for object 'sysdevices'.
DBCC results for 'sysmessages'.
There are 3782 rows in 164 pages for object 'sysmessages'.
DBCC results for 'sysconfigures'.
There are 37 rows in 1 pages for object 'sysconfigures'.
DBCC results for 'sysservers'.
There are 1 rows in 1 pages for object 'sysservers'.
DBCC results for 'syslanguages'.
There are 33 rows in 3 pages for object 'syslanguages'.
DBCC results for 'syscharsets'.
There are 114 rows in 33 pages for object 'syscharsets'.
DBCC results for 'sysaltfiles'.
There are 26 rows in 5 pages for object 'sysaltfiles'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'spt_monitor'.
There are 1 rows in 1 pages for object 'spt_monitor'.
DBCC results for 'spt_values'.
There are 727 rows in 7 pages for object 'spt_values'.
DBCC results for 'spt_fallback_db'.
There are 0 rows in 0 pages for object 'spt_fallback_db'.
DBCC results for 'spt_fallback_dev'.
There are 0 rows in 0 pages for object 'spt_fallback_dev'.
DBCC results for 'spt_fallback_usg'.
There are 0 rows in 0 pages for object 'spt_fallback_usg'.
DBCC results for 'spt_provider_types'.
There are 25 rows in 1 pages for object 'spt_provider_types'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 'spt_datatype_info_ext'.
There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
DBCC results for 'MSreplication_options'.
There are 2 rows in 1 pages for object 'MSreplication_options'.
DBCC results for 'spt_datatype_info'.
There are 36 rows in 1 pages for object 'spt_datatype_info'.
DBCC results for 'spt_server_info'.
There are 29 rows in 1 pages for object 'spt_server_info'.
CHECKDB found 0 allocation errors and 26 consistency errors in database 'master'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (master ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
#####################################################################

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2006-02-05 : 12:27:11

Looks like you need to restore your master DB too. Did the 3rd party attempt this? Why do they believe these errors will be fixed in SP3? (which you should definitely upgrade to)

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.)

ScottH
Starting Member

2 Posts

Posted - 2006-02-06 : 10:09:55

quote:
Originally posted by paulrandal

Looks like you need to restore your master DB too. Did the 3rd party attempt this? Why do they believe these errors will be fixed in SP3? (which you should definitely upgrade to)

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.)

Paul,

The 3rd party did not attempt this and the only explanation I heard was that they did some research on this issue (Possible chain linkage problem)and found that SP3 had a fix for that. My only problem with that was these errors did not exist before the hardware failure.

I have read up some on restoring the master database and I think that is which way I will go and then apply the latest service pack. I tried applying SP3 over the weekend and it errors out at the first script to run.

Thanks for the response.

Scott

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources