Error while connection: msdb

Showing posts with label msdb. Show all posts

Monday, March 26, 2012

Error: 644, Severity: 21, State: 3

I am getting these errors in my event log pertaining to the MSDB
database. I don't have any backups so I can't restore. Can't I just
recreate the system databases? What implications will that cause?
Here's the dbcc checkdb output from QA.
Any insight would be helpful.
Andy
DBCC results for 'msdb'.
DBCC results for 'sysobjects'.
There are 394 rows in 8 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 241 rows in 11 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 3468 rows in 123 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 402 rows in 163 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 185 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 17 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 2567 rows in 17 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 12 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 'sysjobschedules'.
There are 4 rows in 1 pages for object 'sysjobschedules'.
DBCC results for 'RTblIfaceMem'.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3506) is missing a
reference from previous page (1:3505). Possible chain linkage problem.
There are 1189 rows in 6 pages for object 'RTblIfaceMem'.
DBCC results for 'backupfile'.
There are 28046 rows in 460 pages for object 'backupfile'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'backupfile' (object ID 18099105).
DBCC results for 'syscategories'.
There are 19 rows in 1 pages for object 'syscategories'.
DBCC results for 'systargetservers'.
There are 0 rows in 0 pages for object 'systargetservers'.
DBCC results for 'RTblWorkspaceItems'.
There are 0 rows in 0 pages for object 'RTblWorkspaceItems'.
DBCC results for 'restorehistory'.
There are 54 rows in 1 pages for object 'restorehistory'.
DBCC results for 'systargetservergroups'.
There are 0 rows in 0 pages for object 'systargetservergroups'.
DBCC results for 'RTblDatabaseVersion'.
There are 1 rows in 1 pages for object 'RTblDatabaseVersion'.
DBCC results for 'systargetservergroupmembers'.
There are 0 rows in 0 pages for object 'systargetservergroupmembers'.
DBCC results for 'sysalerts'.
There are 9 rows in 1 pages for object 'sysalerts'.
DBCC results for 'RTblDTSProps'.
There are 0 rows in 0 pages for object 'RTblDTSProps'.
DBCC results for 'RTblVersionAdminInfo'.
There are 2333 rows in 22 pages for object 'RTblVersionAdminInfo'.
DBCC results for 'restorefile'.
There are 96 rows in 1 pages for object 'restorefile'.
DBCC results for 'sysoperators'.
There are 0 rows in 0 pages for object 'sysoperators'.
DBCC results for 'sysnotifications'.
There are 0 rows in 0 pages for object 'sysnotifications'.
DBCC results for 'RTblParameterDef'.
There are 136 rows in 2 pages for object 'RTblParameterDef'.
DBCC results for 'restorefilegroup'.
There are 42 rows in 1 pages for object 'restorefilegroup'.
DBCC results for 'systaskids'.
There are 0 rows in 0 pages for object 'systaskids'.
DBCC results for 'syscachedcredentials'.
There are 1 rows in 1 pages for object 'syscachedcredentials'.
DBCC results for 'RTblIfaceHier'.
There are 3349 rows in 12 pages for object 'RTblIfaceHier'.
DBCC results for 'logmarkhistory'.
There are 0 rows in 0 pages for object 'logmarkhistory'.
DBCC results for 'RTblNamedObj'.
There are 2196 rows in 15 pages for object 'RTblNamedObj'.
DBCC results for 'sysdtscategories'.
There are 3 rows in 1 pages for object 'sysdtscategories'.
DBCC results for 'sysdtspackages'.
There are 0 rows in 0 pages for object 'sysdtspackages'.
DBCC results for 'RTblTypeInfo'.
There are 0 rows in 0 pages for object 'RTblTypeInfo'.
DBCC results for 'sysdtspackagelog'.
There are 0 rows in 0 pages for object 'sysdtspackagelog'.
DBCC results for 'RTblScriptDefs'.
There are 0 rows in 0 pages for object 'RTblScriptDefs'.
DBCC results for 'RTblOLPProps'.
There are 0 rows in 0 pages for object 'RTblOLPProps'.
DBCC results for 'sysdtssteplog'.
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:0) identified by (RID = (1:1330:0) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68528) has index values
(sequence_id = 73506 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68528).
There are 0 rows in 0 pages for object 'sysdtssteplog'.
DBCC results for 'RTblEnumerationDef'.
There are 0 rows in 0 pages for object 'RTblEnumerationDef'.
DBCC results for 'sysdtstasklog'.
There are 0 rows in 0 pages for object 'sysdtstasklog'.
DBCC results for 'RTblSumInfo'.
There are 0 rows in 0 pages for object 'RTblSumInfo'.
DBCC results for 'RTblMDSProps'.
There are 0 rows in 0 pages for object 'RTblMDSProps'.
DBCC results for 'RTblEnumerationValueDef'.
There are 0 rows in 0 pages for object 'RTblEnumerationValueDef'.
DBCC results for 'RTblUMLProps'.
There are 0 rows in 0 pages for object 'RTblUMLProps'.
DBCC results for 'sysdbmaintplans'.
There are 2 rows in 1 pages for object 'sysdbmaintplans'.
DBCC results for 'sysdbmaintplan_jobs'.
There are 4 rows in 1 pages for object 'sysdbmaintplan_jobs'.
DBCC results for 'RTblUMXProps'.
There are 0 rows in 0 pages for object 'RTblUMXProps'.
DBCC results for 'sysdbmaintplan_databases'.
There are 1 rows in 1 pages for object 'sysdbmaintplan_databases'.
DBCC results for 'RTblSIMProps'.
There are 0 rows in 0 pages for object 'RTblSIMProps'.
DBCC results for 'sysdbmaintplan_history'.
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:1) identified by (RID = (1:1330:1) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68529) has index values
(sequence_id = 73507 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68529).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:2) identified by (RID = (1:1330:2) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68530) has index values
(sequence_id = 73508 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68530).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:3) identified by (RID = (1:1330:3) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68531) has index values
(sequence_id = 73509 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68531).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:4) identified by (RID = (1:1330:4) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68532) has index values
(sequence_id = 73510 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68532).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:5) identified by (RID = (1:1330:5) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68533) has index values
(sequence_id = 73511 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68533).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:6) identified by (RID = (1:1330:6) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68534) has index values
(sequence_id = 73512 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68534).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:7) identified by (RID = (1:1330:7) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68535) has index values
(sequence_id = 73513 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68535).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:8) identified by (RID = (1:1330:8) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68536) has index values
(sequence_id = 73514 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68536).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:9) identified by (RID = (1:1330:9) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68537) has index values
(sequence_id = 73515 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68537).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:10) identified by (RID = (1:1330:10) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68538) has index values
(sequence_id = 73516 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68538).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:11) identified by (RID = (1:1330:11) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68539) has index values
(sequence_id = 73517 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68539).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:12) identified by (RID = (1:1330:12) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68540) has index values
(sequence_id = 73518 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68540).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:13) identified by (RID = (1:1330:13) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68541) has index values
(sequence_id = 73519 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68541).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:14) identified by (RID = (1:1330:14) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68542) has index values
(sequence_id = 73520 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68542).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:15) identified by (RID = (1:1330:15) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68543) has index values
(sequence_id = 73521 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68543).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:16) identified by (RID = (1:1330:16) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68544) has index values
(sequence_id = 73522 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68544).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:17) identified by (RID = (1:1330:17) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68545) has index values
(sequence_id = 73523 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68545).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:18) identified by (RID = (1:1330:18) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68546) has index values
(sequence_id = 73524 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68546).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:19) identified by (RID = (1:1330:19) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68547) has index values
(sequence_id = 73525 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68547).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:20) identified by (RID = (1:1330:20) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68548) has index values
(sequence_id = 73526 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68548).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:21) identified by (RID = (1:1330:21) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68549) has index values
(sequence_id = 73527 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68549).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:22) identified by (RID = (1:1330:22) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68550) has index values
(sequence_id = 73528 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68550).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:23) identified by (RID = (1:1330:23) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68551) has index values
(sequence_id = 73529 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68551).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:24) identified by (RID = (1:1330:24) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68552) has index values
(sequence_id = 73530 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68552).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:25) identified by (RID = (1:1330:25) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68553) has index values
(sequence_id = 73531 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68553).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:26) identified by (RID = (1:1330:26) plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68554) has index values
(sequence_id = 73532 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68554).
There are 1000 rows in 41 pages for object 'sysdbmaintplan_history'.
CHECKDB found 0 allocation errors and 27 consistency errors in table
'sysdbmaintplan_history' (object ID 1090102924).
DBCC results for 'RTblGENProps'.
There are 0 rows in 0 pages for object 'RTblGENProps'.
DBCC results for 'RTblDTMProps'.
There are 0 rows in 0 pages for object 'RTblDTMProps'.
DBCC results for 'log_shipping_primaries'.
There are 0 rows in 0 pages for object 'log_shipping_primaries'.
DBCC results for 'log_shipping_secondaries'.
There are 0 rows in 0 pages for object 'log_shipping_secondaries'.
DBCC results for 'RTblDBMProps'.
There are 0 rows in 0 pages for object 'RTblDBMProps'.
DBCC results for 'RTblEQMProps'.
There are 0 rows in 0 pages for object 'RTblEQMProps'.
DBCC results for 'mswebtasks'.
There are 0 rows in 0 pages for object 'mswebtasks'.
DBCC results for 'RTblVersions'.
There are 2333 rows in 20 pages for object 'RTblVersions'.
DBCC results for 'RTblDBXProps'.
There are 0 rows in 0 pages for object 'RTblDBXProps'.
DBCC results for 'RTblRelships'.
There are 6922 rows in 97 pages for object 'RTblRelships'.
DBCC results for 'RTblSites'.
There are 44 rows in 1 pages for object 'RTblSites'.
DBCC results for 'RTblProps'.
There are 393 rows in 2 pages for object 'RTblProps'.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index
'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:1542:26) with values (media_family_id = 124C64EE-0000-0000-0000-000000000000 and media_set_id = 18046 and
family_sequence_number = 1.499725856E-305) points to the data row
identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'sysjobhistory.nc1' (ID 2073058421)
(index ID 2). Extra or invalid key for the keys:
DBCC results for 'RTblRelshipProps'.
There are 28 rows in 1 pages for object 'RTblRelshipProps'.
DBCC results for 'RTblPropDefs'.
There are 797 rows in 7 pages for object 'RTblPropDefs'.
DBCC results for 'RTblClassExtension'.
There are 69 rows in 1 pages for object 'RTblClassExtension'.
DBCC results for 'RTblRelColDefs'.
There are 320 rows in 2 pages for object 'RTblRelColDefs'.
DBCC results for 'RTblIfaceDefs'.
There are 453 rows in 4 pages for object 'RTblIfaceDefs'.
DBCC results for 'backupmediaset'.
There are 24118 rows in 249 pages for object 'backupmediaset'.
DBCC results for 'sqlagent_info'.
There are 0 rows in 0 pages for object 'sqlagent_info'.
DBCC results for 'RTblClassDefs'.
There are 537 rows in 5 pages for object 'RTblClassDefs'.
DBCC results for 'sysdownloadlist'.
There are 0 rows in 0 pages for object 'sysdownloadlist'.
DBCC results for 'backupmediafamily'.
There are 24118 rows in 459 pages for object 'backupmediafamily'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'backupmediafamily' (object ID 2069582411).
DBCC results for 'sysjobhistory'.
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:484:0) with values (job_id = 0C4E74E1-FFCD-4812-B456-6F563B61D3D6 and instance_id = 5909) points to
the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'sysjobhistory.nc1' (ID 2073058421)
(index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:484:1) with values (job_id = 0C4E74E1-FFCD-4812-B456-6F563B61D3D6 and instance_id = 5910) points to
the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupset.backupsetuuid' (ID
2117582582) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:331:138) with values (backup_set_uuid = C89DADB3-32FA-4F2C-A0FC-88897BDF8DCE and backup_set_id = 18058) points
to the data row identified by ().
There are 2354 rows in 134 pages for object 'sysjobhistory'.
CHECKDB found 0 allocation errors and 2 consistency errors in table
'sysjobhistory' (object ID 2073058421).
DBCC results for 'sysjobs'.
There are 4 rows in 1 pages for object 'sysjobs'.
DBCC results for 'RTblTFMProps'.
There are 0 rows in 0 pages for object 'RTblTFMProps'.
DBCC results for 'RTblRelshipDefs'.
There are 144 rows in 1 pages for object 'RTblRelshipDefs'.
DBCC results for 'backupset'.
There are 24122 rows in 1050 pages for object 'backupset'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'backupset' (object ID 2117582582).
DBCC results for 'sysjobservers'.
There are 4 rows in 1 pages for object 'sysjobservers'.
DBCC results for 'RTblTypeLibs'.
There are 17 rows in 1 pages for object 'RTblTypeLibs'.
DBCC results for 'sysjobsteps'.
There are 4 rows in 1 pages for object 'sysjobsteps'.
CHECKDB found 0 allocation errors and 32 consistency errors in database
'msdb'.
repair_rebuild is the minimum repair level for the errors found by DBCC
CHECKDB (msdb ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.You could try instmsdb.sql (Google and you should find info on how to run the script). Or perhaps
try to run CHECKDB with the recommended repair option (see the text at the very end of the DBCC
command). Btw, a tip: run CHECKDB using the WITH NO_INFOMSGS option so we only see the errors and
get rid of informational messages...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<andyleffler@.bellsouth.net> wrote in message
news:1147793712.390091.193320@.i39g2000cwa.googlegroups.com...
>I am getting these errors in my event log pertaining to the MSDB
> database. I don't have any backups so I can't restore. Can't I just
> recreate the system databases? What implications will that cause?
> Here's the dbcc checkdb output from QA.
> Any insight would be helpful.
> Andy
> DBCC results for 'msdb'.
> DBCC results for 'sysobjects'.
> There are 394 rows in 8 pages for object 'sysobjects'.
> DBCC results for 'sysindexes'.
> There are 241 rows in 11 pages for object 'sysindexes'.
> DBCC results for 'syscolumns'.
> There are 3468 rows in 123 pages for object 'syscolumns'.
> DBCC results for 'systypes'.
> There are 26 rows in 1 pages for object 'systypes'.
> DBCC results for 'syscomments'.
> There are 402 rows in 163 pages for object 'syscomments'.
> DBCC results for 'sysfiles1'.
> There are 2 rows in 1 pages for object 'sysfiles1'.
> DBCC results for 'syspermissions'.
> There are 185 rows in 1 pages for object 'syspermissions'.
> DBCC results for 'sysusers'.
> There are 17 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 2567 rows in 17 pages for object 'sysdepends'.
> DBCC results for 'sysreferences'.
> There are 12 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 'sysjobschedules'.
> There are 4 rows in 1 pages for object 'sysjobschedules'.
> DBCC results for 'RTblIfaceMem'.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 18099105, index ID 1. Page (1:3506) is missing a
> reference from previous page (1:3505). Possible chain linkage problem.
> There are 1189 rows in 6 pages for object 'RTblIfaceMem'.
> DBCC results for 'backupfile'.
> There are 28046 rows in 460 pages for object 'backupfile'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'backupfile' (object ID 18099105).
> DBCC results for 'syscategories'.
> There are 19 rows in 1 pages for object 'syscategories'.
> DBCC results for 'systargetservers'.
> There are 0 rows in 0 pages for object 'systargetservers'.
> DBCC results for 'RTblWorkspaceItems'.
> There are 0 rows in 0 pages for object 'RTblWorkspaceItems'.
> DBCC results for 'restorehistory'.
> There are 54 rows in 1 pages for object 'restorehistory'.
> DBCC results for 'systargetservergroups'.
> There are 0 rows in 0 pages for object 'systargetservergroups'.
> DBCC results for 'RTblDatabaseVersion'.
> There are 1 rows in 1 pages for object 'RTblDatabaseVersion'.
> DBCC results for 'systargetservergroupmembers'.
> There are 0 rows in 0 pages for object 'systargetservergroupmembers'.
> DBCC results for 'sysalerts'.
> There are 9 rows in 1 pages for object 'sysalerts'.
> DBCC results for 'RTblDTSProps'.
> There are 0 rows in 0 pages for object 'RTblDTSProps'.
> DBCC results for 'RTblVersionAdminInfo'.
> There are 2333 rows in 22 pages for object 'RTblVersionAdminInfo'.
> DBCC results for 'restorefile'.
> There are 96 rows in 1 pages for object 'restorefile'.
> DBCC results for 'sysoperators'.
> There are 0 rows in 0 pages for object 'sysoperators'.
> DBCC results for 'sysnotifications'.
> There are 0 rows in 0 pages for object 'sysnotifications'.
> DBCC results for 'RTblParameterDef'.
> There are 136 rows in 2 pages for object 'RTblParameterDef'.
> DBCC results for 'restorefilegroup'.
> There are 42 rows in 1 pages for object 'restorefilegroup'.
> DBCC results for 'systaskids'.
> There are 0 rows in 0 pages for object 'systaskids'.
> DBCC results for 'syscachedcredentials'.
> There are 1 rows in 1 pages for object 'syscachedcredentials'.
> DBCC results for 'RTblIfaceHier'.
> There are 3349 rows in 12 pages for object 'RTblIfaceHier'.
> DBCC results for 'logmarkhistory'.
> There are 0 rows in 0 pages for object 'logmarkhistory'.
> DBCC results for 'RTblNamedObj'.
> There are 2196 rows in 15 pages for object 'RTblNamedObj'.
> DBCC results for 'sysdtscategories'.
> There are 3 rows in 1 pages for object 'sysdtscategories'.
> DBCC results for 'sysdtspackages'.
> There are 0 rows in 0 pages for object 'sysdtspackages'.
> DBCC results for 'RTblTypeInfo'.
> There are 0 rows in 0 pages for object 'RTblTypeInfo'.
> DBCC results for 'sysdtspackagelog'.
> There are 0 rows in 0 pages for object 'sysdtspackagelog'.
> DBCC results for 'RTblScriptDefs'.
> There are 0 rows in 0 pages for object 'RTblScriptDefs'.
> DBCC results for 'RTblOLPProps'.
> There are 0 rows in 0 pages for object 'RTblOLPProps'.
> DBCC results for 'sysdtssteplog'.
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:0) identified by (RID = (1:1330:0) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68528) has index values
> (sequence_id = 73506 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68528).
> There are 0 rows in 0 pages for object 'sysdtssteplog'.
> DBCC results for 'RTblEnumerationDef'.
> There are 0 rows in 0 pages for object 'RTblEnumerationDef'.
> DBCC results for 'sysdtstasklog'.
> There are 0 rows in 0 pages for object 'sysdtstasklog'.
> DBCC results for 'RTblSumInfo'.
> There are 0 rows in 0 pages for object 'RTblSumInfo'.
> DBCC results for 'RTblMDSProps'.
> There are 0 rows in 0 pages for object 'RTblMDSProps'.
> DBCC results for 'RTblEnumerationValueDef'.
> There are 0 rows in 0 pages for object 'RTblEnumerationValueDef'.
> DBCC results for 'RTblUMLProps'.
> There are 0 rows in 0 pages for object 'RTblUMLProps'.
> DBCC results for 'sysdbmaintplans'.
> There are 2 rows in 1 pages for object 'sysdbmaintplans'.
> DBCC results for 'sysdbmaintplan_jobs'.
> There are 4 rows in 1 pages for object 'sysdbmaintplan_jobs'.
> DBCC results for 'RTblUMXProps'.
> There are 0 rows in 0 pages for object 'RTblUMXProps'.
> DBCC results for 'sysdbmaintplan_databases'.
> There are 1 rows in 1 pages for object 'sysdbmaintplan_databases'.
> DBCC results for 'RTblSIMProps'.
> There are 0 rows in 0 pages for object 'RTblSIMProps'.
> DBCC results for 'sysdbmaintplan_history'.
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:1) identified by (RID = (1:1330:1) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68529) has index values
> (sequence_id = 73507 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68529).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:2) identified by (RID = (1:1330:2) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68530) has index values
> (sequence_id = 73508 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68530).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:3) identified by (RID = (1:1330:3) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68531) has index values
> (sequence_id = 73509 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68531).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:4) identified by (RID = (1:1330:4) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68532) has index values
> (sequence_id = 73510 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68532).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:5) identified by (RID = (1:1330:5) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68533) has index values
> (sequence_id = 73511 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68533).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:6) identified by (RID = (1:1330:6) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68534) has index values
> (sequence_id = 73512 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68534).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:7) identified by (RID = (1:1330:7) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68535) has index values
> (sequence_id = 73513 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68535).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:8) identified by (RID = (1:1330:8) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68536) has index values
> (sequence_id = 73514 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68536).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:9) identified by (RID = (1:1330:9) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68537) has index values
> (sequence_id = 73515 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68537).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:10) identified by (RID = (1:1330:10) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68538) has index values
> (sequence_id = 73516 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68538).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:11) identified by (RID = (1:1330:11) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68539) has index values
> (sequence_id = 73517 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68539).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:12) identified by (RID = (1:1330:12) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68540) has index values
> (sequence_id = 73518 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68540).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:13) identified by (RID = (1:1330:13) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68541) has index values
> (sequence_id = 73519 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68541).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:14) identified by (RID = (1:1330:14) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68542) has index values
> (sequence_id = 73520 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68542).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:15) identified by (RID = (1:1330:15) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68543) has index values
> (sequence_id = 73521 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68543).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:16) identified by (RID = (1:1330:16) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68544) has index values
> (sequence_id = 73522 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68544).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:17) identified by (RID = (1:1330:17) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68545) has index values
> (sequence_id = 73523 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68545).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:18) identified by (RID = (1:1330:18) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68546) has index values
> (sequence_id = 73524 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68546).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:19) identified by (RID = (1:1330:19) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68547) has index values
> (sequence_id = 73525 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68547).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:20) identified by (RID = (1:1330:20) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68548) has index values
> (sequence_id = 73526 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68548).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:21) identified by (RID = (1:1330:21) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68549) has index values
> (sequence_id = 73527 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68549).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:22) identified by (RID = (1:1330:22) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68550) has index values
> (sequence_id = 73528 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68550).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:23) identified by (RID = (1:1330:23) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68551) has index values
> (sequence_id = 73529 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68551).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:24) identified by (RID = (1:1330:24) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68552) has index values
> (sequence_id = 73530 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68552).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:25) identified by (RID = (1:1330:25) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68553) has index values
> (sequence_id = 73531 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68553).
> Server: Msg 8951, Level 16, State 1, Line 1
> Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
> invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
> row:
> Server: Msg 8955, Level 16, State 1, Line 1
> Data row (1:1330:26) identified by (RID = (1:1330:26) plan_id => 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68554) has index values
> (sequence_id = 73532 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
> and ? = 68554).
> There are 1000 rows in 41 pages for object 'sysdbmaintplan_history'.
> CHECKDB found 0 allocation errors and 27 consistency errors in table
> 'sysdbmaintplan_history' (object ID 1090102924).
> DBCC results for 'RTblGENProps'.
> There are 0 rows in 0 pages for object 'RTblGENProps'.
> DBCC results for 'RTblDTMProps'.
> There are 0 rows in 0 pages for object 'RTblDTMProps'.
> DBCC results for 'log_shipping_primaries'.
> There are 0 rows in 0 pages for object 'log_shipping_primaries'.
> DBCC results for 'log_shipping_secondaries'.
> There are 0 rows in 0 pages for object 'log_shipping_secondaries'.
> DBCC results for 'RTblDBMProps'.
> There are 0 rows in 0 pages for object 'RTblDBMProps'.
> DBCC results for 'RTblEQMProps'.
> There are 0 rows in 0 pages for object 'RTblEQMProps'.
> DBCC results for 'mswebtasks'.
> There are 0 rows in 0 pages for object 'mswebtasks'.
> DBCC results for 'RTblVersions'.
> There are 2333 rows in 20 pages for object 'RTblVersions'.
> DBCC results for 'RTblDBXProps'.
> There are 0 rows in 0 pages for object 'RTblDBXProps'.
> DBCC results for 'RTblRelships'.
> There are 6922 rows in 97 pages for object 'RTblRelships'.
> DBCC results for 'RTblSites'.
> There are 44 rows in 1 pages for object 'RTblSites'.
> DBCC results for 'RTblProps'.
> There are 393 rows in 2 pages for object 'RTblProps'.
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'msdb', index
> 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:1542:26) with values (media_family_id => 124C64EE-0000-0000-0000-000000000000 and media_set_id = 18046 and
> family_sequence_number = 1.499725856E-305) points to the data row
> identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'msdb', index 'sysjobhistory.nc1' (ID 2073058421)
> (index ID 2). Extra or invalid key for the keys:
> DBCC results for 'RTblRelshipProps'.
> There are 28 rows in 1 pages for object 'RTblRelshipProps'.
> DBCC results for 'RTblPropDefs'.
> There are 797 rows in 7 pages for object 'RTblPropDefs'.
> DBCC results for 'RTblClassExtension'.
> There are 69 rows in 1 pages for object 'RTblClassExtension'.
> DBCC results for 'RTblRelColDefs'.
> There are 320 rows in 2 pages for object 'RTblRelColDefs'.
> DBCC results for 'RTblIfaceDefs'.
> There are 453 rows in 4 pages for object 'RTblIfaceDefs'.
> DBCC results for 'backupmediaset'.
> There are 24118 rows in 249 pages for object 'backupmediaset'.
> DBCC results for 'sqlagent_info'.
> There are 0 rows in 0 pages for object 'sqlagent_info'.
> DBCC results for 'RTblClassDefs'.
> There are 537 rows in 5 pages for object 'RTblClassDefs'.
> DBCC results for 'sysdownloadlist'.
> There are 0 rows in 0 pages for object 'sysdownloadlist'.
> DBCC results for 'backupmediafamily'.
> There are 24118 rows in 459 pages for object 'backupmediafamily'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'backupmediafamily' (object ID 2069582411).
> DBCC results for 'sysjobhistory'.
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:484:0) with values (job_id => 0C4E74E1-FFCD-4812-B456-6F563B61D3D6 and instance_id = 5909) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'msdb', index 'sysjobhistory.nc1' (ID 2073058421)
> (index ID 2). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:484:1) with values (job_id => 0C4E74E1-FFCD-4812-B456-6F563B61D3D6 and instance_id = 5910) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'msdb', index 'backupset.backupsetuuid' (ID
> 2117582582) (index ID 2). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:331:138) with values (backup_set_uuid => C89DADB3-32FA-4F2C-A0FC-88897BDF8DCE and backup_set_id = 18058) points
> to the data row identified by ().
> There are 2354 rows in 134 pages for object 'sysjobhistory'.
> CHECKDB found 0 allocation errors and 2 consistency errors in table
> 'sysjobhistory' (object ID 2073058421).
> DBCC results for 'sysjobs'.
> There are 4 rows in 1 pages for object 'sysjobs'.
> DBCC results for 'RTblTFMProps'.
> There are 0 rows in 0 pages for object 'RTblTFMProps'.
> DBCC results for 'RTblRelshipDefs'.
> There are 144 rows in 1 pages for object 'RTblRelshipDefs'.
> DBCC results for 'backupset'.
> There are 24122 rows in 1050 pages for object 'backupset'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'backupset' (object ID 2117582582).
> DBCC results for 'sysjobservers'.
> There are 4 rows in 1 pages for object 'sysjobservers'.
> DBCC results for 'RTblTypeLibs'.
> There are 17 rows in 1 pages for object 'RTblTypeLibs'.
> DBCC results for 'sysjobsteps'.
> There are 4 rows in 1 pages for object 'sysjobsteps'.
> CHECKDB found 0 allocation errors and 32 consistency errors in database
> 'msdb'.
> repair_rebuild is the minimum repair level for the errors found by DBCC
> CHECKDB (msdb ).
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>|||Tibor,
What will I have to do after I run the instmsdb.sql script? Will I lose
anything important? I don't have any important jobs. I can recreate
those.
here's the output WITH NO_INFOMSGS
Thanks for your help.
Andy
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3506) is missing a
reference from previous page (1:3505). Possible chain linkage problem.
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:0) identified by (RID = (1:1330:0) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68528) has index values
(sequence_id = 73506 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68528).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:1) identified by (RID = (1:1330:1) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68529) has index values
(sequence_id = 73507 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68529).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:2) identified by (RID = (1:1330:2) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68530) has index values
(sequence_id = 73508 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68530).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:3) identified by (RID = (1:1330:3) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68531) has index values
(sequence_id = 73509 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68531).
CHECKDB found 0 allocation errors and 1 consistency errors in table
'backupfile' (object ID 18099105).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:4) identified by (RID = (1:1330:4) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68532) has index values
(sequence_id = 73510 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68532).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:5) identified by (RID = (1:1330:5) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68533) has index values
(sequence_id = 73511 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68533).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:6) identified by (RID = (1:1330:6) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68534) has index values
(sequence_id = 73512 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68534).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:7) identified by (RID = (1:1330:7) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68535) has index values
(sequence_id = 73513 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68535).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:8) identified by (RID = (1:1330:8) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68536) has index values
(sequence_id = 73514 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68536).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:9) identified by (RID = (1:1330:9) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68537) has index values
(sequence_id = 73515 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68537).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:10) identified by (RID = (1:1330:10) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68538) has index values
(sequence_id = 73516 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68538).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:11) identified by (RID = (1:1330:11) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68539) has index values
(sequence_id = 73517 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68539).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:12) identified by (RID = (1:1330:12) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68540) has index values
(sequence_id = 73518 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68540).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:13) identified by (RID = (1:1330:13) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68541) has index values
(sequence_id = 73519 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68541).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:14) identified by (RID = (1:1330:14) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68542) has index values
(sequence_id = 73520 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68542).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:15) identified by (RID = (1:1330:15) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68543) has index values
(sequence_id = 73521 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68543).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:16) identified by (RID = (1:1330:16) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68544) has index values
(sequence_id = 73522 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68544).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:17) identified by (RID = (1:1330:17) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68545) has index values
(sequence_id = 73523 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68545).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:18) identified by (RID = (1:1330:18) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68546) has index values
(sequence_id = 73524 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68546).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:19) identified by (RID = (1:1330:19) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68547) has index values
(sequence_id = 73525 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68547).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:20) identified by (RID = (1:1330:20) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68548) has index values
(sequence_id = 73526 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68548).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:21) identified by (RID = (1:1330:21) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68549) has index values
(sequence_id = 73527 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68549).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:22) identified by (RID = (1:1330:22) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68550) has index values
(sequence_id = 73528 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68550).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:23) identified by (RID = (1:1330:23) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68551) has index values
(sequence_id = 73529 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68551).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:24) identified by (RID = (1:1330:24) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68552) has index values
(sequence_id = 73530 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68552).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:25) identified by (RID = (1:1330:25) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68553) has index values
(sequence_id = 73531 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68553).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'sysdbmaintplan_history' (ID 1090102924). Missing or
invalid key in index 'UQ__sysdbmaintplan_h__41EDCAC5' (ID 2) for the
row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:1330:26) identified by (RID = (1:1330:26) plan_id =774C472B-B47C-4AC5-8EA9-F4FC76B68F8B and ? = 68554) has index values
(sequence_id = 73532 and plan_id = 774C472B-B47C-4AC5-8EA9-F4FC76B68F8B
and ? = 68554).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index
'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:1542:26) with values (media_family_id =124C64EE-0000-0000-0000-000000000000 and media_set_id = 18046 and
family_sequence_number = 1.499725856E-305) points to the data row
identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'sysjobhistory.nc1' (ID 2073058421)
(index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:484:0) with values (job_id =0C4E74E1-FFCD-4812-B456-6F563B61D3D6 and instance_id = 5909) points to
the data row identified by ().
CHECKDB found 0 allocation errors and 27 consistency errors in table
'sysdbmaintplan_history' (object ID 1090102924).
CHECKDB found 0 allocation errors and 1 consistency errors in table
'backupmediafamily' (object ID 2069582411).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'sysjobhistory.nc1' (ID 2073058421)
(index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:484:1) with values (job_id =0C4E74E1-FFCD-4812-B456-6F563B61D3D6 and instance_id = 5910) points to
the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupset.backupsetuuid' (ID
2117582582) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:331:138) with values (backup_set_uuid =C89DADB3-32FA-4F2C-A0FC-88897BDF8DCE and backup_set_id = 18058) points
to the data row identified by ().
CHECKDB found 0 allocation errors and 2 consistency errors in table
'sysjobhistory' (object ID 2073058421).
CHECKDB found 0 allocation errors and 1 consistency errors in table
'backupset' (object ID 2117582582).
CHECKDB found 0 allocation errors and 32 consistency errors in database
'msdb'.
repair_rebuild is the minimum repair level for the errors found by DBCC
CHECKDB (msdb ).|||I got it. I put the database into single user mode then ran DBCC
CHECKDB (databasename', Repair_Rebuild) several times until all the
errors disappeared.
Thanks for your help.
Andy

Thursday, March 22, 2012

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
JeffSome anti-virus software perhaps?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> > Every couple of weeks it appears that my MSDB database is getting
> > corrupt. Here is my situation.
> > Everyday at 4 am I take a backup off all the instances, then at 5 am
> > the computer reboots. Once the computer is up all the instances try to
> > start up except MSDB will have a problem. When I log into Enterprise
> > Manager the instance is listed as Suspect. I have to restore the
> > database from the backup taken at 4 am and everything is fine.
> > Here is the error from the log file the last time it happened.
> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> > But I have also received this error:
> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> > process cannot access the file because it is being used by another
> > process.) during the creation/opening of physical device C:\Program
> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> > for virtual device number (VDN) 1.
> > I have no idea what this other process would be.
> > Any ideas?
> > Thanks,
> > Jeff
It might be possible but why always the same database each time?|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
--
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> > Every couple of weeks it appears that my MSDB database is getting
> > corrupt. Here is my situation.
> > Everyday at 4 am I take a backup off all the instances, then at 5 am
> > the computer reboots. Once the computer is up all the instances try to
> > start up except MSDB will have a problem. When I log into Enterprise
> > Manager the instance is listed as Suspect. I have to restore the
> > database from the backup taken at 4 am and everything is fine.
> > Here is the error from the log file the last time it happened.
> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> > But I have also received this error:
> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> > process cannot access the file because it is being used by another
> > process.) during the creation/opening of physical device C:\Program
> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> > for virtual device number (VDN) 1.
> > I have no idea what this other process would be.
> > Any ideas?
> > Thanks,
> > Jeff
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to exclude them... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegroups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
>> Try excluding msdb from the backup and see if you get the same error
>> post-reboot. Also if you skip the reboot, does sql continue indefinitely
>> without a problem?
>> Someone mentioned antivirus. Not sure that would cause your particular
>> issue, but you do have the AV set to exclude .mdf and .ldf file types,
>> right?
>> --
>> TheSQLGuru
>> President
>> Indicium Resources, Inc.
>> <jeffchi...@.gmail.com> wrote in message
>> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
>> > Every couple of weeks it appears that my MSDB database is getting
>> > corrupt. Here is my situation.
>> > Everyday at 4 am I take a backup off all the instances, then at 5 am
>> > the computer reboots. Once the computer is up all the instances try to
>> > start up except MSDB will have a problem. When I log into Enterprise
>> > Manager the instance is listed as Suspect. I have to restore the
>> > database from the backup taken at 4 am and everything is fine.
>> > Here is the error from the log file the last time it happened.
>> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
>> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
>> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
>> > But I have also received this error:
>> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
>> > process cannot access the file because it is being used by another
>> > process.) during the creation/opening of physical device C:\Program
>> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
>> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
>> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
>> > for virtual device number (VDN) 1.
>> > I have no idea what this other process would be.
>> > Any ideas?
>> > Thanks,
>> > Jeff
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>

Monday, March 26, 2012

Error: 644, Severity: 21, State: 3

Thursday, March 22, 2012

Error: 5105 on MSDB database

Error: 5105 on MSDB database

Error: 5105 on MSDB database

Error while connection

Blog Archive

About Me