Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

MDMP files Expand / Collapse
Author
Message
Posted Tuesday, October 30, 2012 4:55 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, June 10, 2013 3:10 AM
Points: 54, Visits: 255
Hi,

In one of my production server, am seeing many MDMP files created on Oct 24. I just refreshed my mind and on Oct 23 we had a server refresh on this server. After the refresh, the database was accessible however our applications was unable to access few objects. They were getting the below error.

Alarm Details: MSSQLSERVER: [8646] Unable to find index entry in index ID 0, of table 906486308, in database 'witness'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.

when i perfromed DBCC i got the below error.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:29593) in object ID 906486308, index ID 0, partition ID 59407486681088, alloc unit ID 59407486681088 (type In-row data). Expected value 100_PCT_FULL, actual value 95_PCT_FULL.

since the object moved to some other allocation unit we restored the database.

After 24th oct i couldnt see any MDMP files. And on oct 28th DBCC check db had run and it gave 54 consistency errors on MSDB database.

When i checked the object id it is related to backupmedia, backup file, backupmediafamily on MSDB. Pasting the sample DBCC check result

DBCC results for 'backupmediaset'.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1858105660, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594047168512 (type In-row data). Page (1:1624) is missing a reference from previous page (1:1665). Possible chain linkage problem.
There are 1668 rows in 24 pages for object "backupmediaset".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediaset' (object ID 1858105660).
DBCC results for 'sysmail_log'.
There are 22 rows in 1 pages for object "sysmail_log".
DBCC results for 'backupmediafamily'.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1890105774, index ID 1, partition ID 72057594042908672, alloc unit ID 72057594047299584 (type In-row data). Page (1:1587) is missing a reference from previous page (1:1586). Possible chain linkage problem.
There are 1637 rows in 33 pages for object "backupmediafamily".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediafamily' (object ID 1890105774).
DBCC results for 'sysdtspackages90'.
There are 2 rows in 1 pages for object "sysdtspackages90".
DBCC results for 'backupset'.
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 41, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1604), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data)

Am very much worried of my Prod database.
Kindly assist me. Thanks in Advance.


Thanks,
Dev.
(+91)89398-14749


Post #1378680
Posted Tuesday, October 30, 2012 10:54 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, August 13, 2014 10:51 PM
Points: 112, Visits: 1,209
'Msg 8914, Level 16, State 1, Line 1' error means that the PFS page (see this blog post) has the wrong free-space tracking bits for a text page. In SQL Server 2000, the algorithm to keep track of free space in the PFS pages wasn't perfect so CHECKDB never reported these errors - it would silently fix them. In 2005 we fixed the algorithm (supposedly), so I turned on the reporting of these errors again in CHECKDB.

Plz check this post to detail information: http://www.sqlskills.com/blogs/paul/post/Corruption-bug-that-people-are-hitting-Msg-8914-PFS-free-space.aspx


SQL Database Recovery Expert
Post #1379148
Posted Wednesday, October 31, 2012 1:49 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:41 AM
Points: 42,827, Visits: 35,957
Please run the following and post the full and complete, unedited output

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Run that on any database that's had any related error and post them all.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1379177
Posted Wednesday, October 31, 2012 1:51 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:41 AM
Points: 42,827, Visits: 35,957
prettsons (10/30/2012)
'Msg 8914, Level 16, State 1, Line 1' error means that the PFS page (see this blog post) has the wrong free-space tracking bits for a text page. In SQL Server 2000, the algorithm to keep track of free space in the PFS pages wasn't perfect so CHECKDB never reported these errors - it would silently fix them. In 2005 we fixed the algorithm (supposedly), so I turned on the reporting of these errors again in CHECKDB.


Not cool to put Paul's words into your paragraph without any indication they're quoted. Makes it look like you were the one who worked on the storage engine team and wrote parts of CheckDB (since that paragraph is written in 1st person).



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1379178
Posted Wednesday, October 31, 2012 9:50 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, June 10, 2013 3:10 AM
Points: 54, Visits: 255
Hi,

Please find the DBCC output ran with NO_INFOMSGS.

Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 117575457, index ID 1, partition ID 72057594039369728, alloc unit ID 72057594043367424 (type In-row data). Page (1:864) is missing a reference from previous page (1:799). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sysjobhistory' (object ID 117575457).
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1858105660, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594047168512 (type In-row data). Page (1:1624) is missing a reference from previous page (1:1665). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediaset' (object ID 1858105660).
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1890105774, index ID 1, partition ID 72057594042908672, alloc unit ID 72057594047299584 (type In-row data). Page (1:1587) is missing a reference from previous page (1:1586). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediafamily' (object ID 1890105774).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 41, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1604), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 42, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1605), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 43, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1606), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 44, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1607), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1604) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1605) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1606) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1607) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1609), whose header indicates that it is allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data). Page (1:1609) is missing a reference from previous page (1:593). Possible chain linkage problem.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data). Page (1:1632) is missing a reference from previous page (1:1607). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 11 consistency errors in table 'backupset' (object ID 1954106002).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:692), slot 12, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), refers to page (1:1609), slot 0, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1609) allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1610) is missing a reference from previous page (1:1609). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1617), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1617) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1618), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1618) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1619), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1619) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1620), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1620) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1621), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1621) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1622), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1622) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1623), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1623) is missing a reference from previous page (1:597). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 17 consistency errors in table 'backupfilegroup' (object ID 2002106173).
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1604), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1604) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1605), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1605) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1606), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1606) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1607), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1607) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1617) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1618) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1619) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1620) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1621) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1622) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1623) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1640) is missing a reference from previous page (1:1623). Possible chain linkage problem.
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 68, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1617), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 69, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1618), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 70, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1619), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 71, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1620), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 72, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1621), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 73, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1622), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 74, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1623), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
CHECKDB found 0 allocation errors and 23 consistency errors in table 'backupfile' (object ID 2050106344).
CHECKDB found 0 allocation errors and 54 consistency errors in database 'msdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msdb).


Please find the DBCC output with ALL_ERRORMSGS


DBCC results for 'msdb'.
Service Broker Msg 9675, State 1: Message Types analyzed: 16.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 7.
Service Broker Msg 9667, State 1: Services analyzed: 5.
Service Broker Msg 9668, State 1: Service Queues analyzed: 5.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results for 'sys.sysrowsetcolumns'.
There are 1580 rows in 12 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 239 rows in 2 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 279 rows in 3 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syshobtcolumns'.
There are 1580 rows in 12 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 239 rows in 2 pages for object "sys.syshobts".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysserefs'.
There are 279 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 22 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 326 rows in 3 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 755 rows in 14 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 2962 rows in 56 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 2 rows in 1 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 0 rows in 0 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 27 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 411 rows in 6 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 571 rows in 5 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 28 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysobjvalues'.
There are 914 rows in 234 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 22 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 1 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 1 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 1 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 345 rows in 2 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 2934 rows in 21 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysqnames'.
There are 91 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 93 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 97 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 17 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 618 rows in 23 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 0 rows in 0 pages for object "sys.sysbinsubobjs".
DBCC results for 'syssubsystems'.
There are 11 rows in 1 pages for object "syssubsystems".
DBCC results for 'sysproxysubsystem'.
There are 0 rows in 0 pages for object "sysproxysubsystem".
DBCC results for 'restorefilegroup'.
There are 4 rows in 1 pages for object "restorefilegroup".
DBCC results for 'sysproxylogin'.
There are 0 rows in 0 pages for object "sysproxylogin".
DBCC results for 'logmarkhistory'.
There are 0 rows in 0 pages for object "logmarkhistory".
DBCC results for 'sqlagent_info'.
There are 0 rows in 0 pages for object "sqlagent_info".
DBCC results for 'suspect_pages'.
There are 0 rows in 0 pages for object "suspect_pages".
DBCC results for 'sysdownloadlist'.
There are 0 rows in 0 pages for object "sysdownloadlist".
DBCC results for 'sysjobhistory'.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 117575457, index ID 1, partition ID 72057594039369728, alloc unit ID 72057594043367424 (type In-row data). Page (1:864) is missing a reference from previous page (1:799). Possible chain linkage problem.
There are 100 rows in 18 pages for object "sysjobhistory".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sysjobhistory' (object ID 117575457).
DBCC results for 'log_shipping_primary_databases'.
There are 0 rows in 0 pages for object "log_shipping_primary_databases".
DBCC results for 'sysdtscategories'.
There are 3 rows in 1 pages for object "sysdtscategories".
DBCC results for 'sysoriginatingservers'.
There are 0 rows in 0 pages for object "sysoriginatingservers".
DBCC results for 'log_shipping_primary_secondaries'.
There are 0 rows in 0 pages for object "log_shipping_primary_secondaries".
DBCC results for 'sysdtspackages'.
There are 0 rows in 0 pages for object "sysdtspackages".
DBCC results for 'log_shipping_monitor_primary'.
There are 0 rows in 0 pages for object "log_shipping_monitor_primary".
DBCC results for 'log_shipping_monitor_history_detail'.
There are 0 rows in 0 pages for object "log_shipping_monitor_history_detail".
DBCC results for 'log_shipping_monitor_error_detail'.
There are 0 rows in 0 pages for object "log_shipping_monitor_error_detail".
DBCC results for 'log_shipping_secondary'.
There are 0 rows in 0 pages for object "log_shipping_secondary".
DBCC results for 'sysjobs'.
There are 7 rows in 1 pages for object "sysjobs".
DBCC results for 'log_shipping_secondary_databases'.
There are 0 rows in 0 pages for object "log_shipping_secondary_databases".
DBCC results for 'sysjobservers'.
There are 7 rows in 1 pages for object "sysjobservers".
DBCC results for 'log_shipping_monitor_secondary'.
There are 0 rows in 0 pages for object "log_shipping_monitor_secondary".
DBCC results for 'syssessions'.
There are 81 rows in 1 pages for object "syssessions".
DBCC results for 'log_shipping_monitor_alert'.
There are 0 rows in 0 pages for object "log_shipping_monitor_alert".
DBCC results for 'sysjobactivity'.
There are 460 rows in 8 pages for object "sysjobactivity".
DBCC results for 'sysjobsteps'.
There are 15 rows in 1 pages for object "sysjobsteps".
DBCC results for 'sysjobstepslogs'.
There are 0 rows in 1 pages for object "sysjobstepslogs".
DBCC results for 'sysdtspackagelog'.
There are 0 rows in 0 pages for object "sysdtspackagelog".
DBCC results for 'sysdtssteplog'.
There are 0 rows in 0 pages for object "sysdtssteplog".
DBCC results for 'sysschedules'.
There are 7 rows in 1 pages for object "sysschedules".
DBCC results for 'sysdtstasklog'.
There are 0 rows in 0 pages for object "sysdtstasklog".
DBCC results for 'DTA_input'.
There are 0 rows in 0 pages for object "DTA_input".
DBCC results for 'sysjobschedules'.
There are 7 rows in 1 pages for object "sysjobschedules".
DBCC results for 'syscategories'.
There are 21 rows in 1 pages for object "syscategories".
DBCC results for 'systargetservers'.
There are 0 rows in 0 pages for object "systargetservers".
DBCC results for 'DTA_progress'.
There are 0 rows in 0 pages for object "DTA_progress".
DBCC results for 'systargetservergroups'.
There are 0 rows in 0 pages for object "systargetservergroups".
DBCC results for 'systargetservergroupmembers'.
There are 0 rows in 0 pages for object "systargetservergroupmembers".
DBCC results for 'sysalerts'.
There are 0 rows in 0 pages for object "sysalerts".
DBCC results for 'sysmail_profile'.
There are 1 rows in 1 pages for object "sysmail_profile".
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 'sysmaintplan_subplans'.
There are 3 rows in 1 pages for object "sysmaintplan_subplans".
DBCC results for 'DTA_output'.
There are 0 rows in 0 pages for object "DTA_output".
DBCC results for 'sys.queue_messages_843150049'.
There are 0 rows in 1 pages for object "sys.queue_messages_843150049".
DBCC results for 'sysmail_principalprofile'.
There are 1 rows in 1 pages for object "sysmail_principalprofile".
DBCC results for 'sys.queue_messages_875150163'.
There are 0 rows in 1 pages for object "sys.queue_messages_875150163".
DBCC results for 'sysmaintplan_log'.
There are 4 rows in 2 pages for object "sysmaintplan_log".
DBCC results for 'DTA_tuninglog'.
There are 0 rows in 0 pages for object "DTA_tuninglog".
DBCC results for 'sysmaintplan_logdetail'.
There are 10 rows in 2 pages for object "sysmaintplan_logdetail".
DBCC results for 'DTA_reports_database'.
There are 0 rows in 0 pages for object "DTA_reports_database".
DBCC results for 'sysmail_account'.
There are 1 rows in 1 pages for object "sysmail_account".
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 'DTA_reports_partitionfunction'.
There are 0 rows in 0 pages for object "DTA_reports_partitionfunction".
DBCC results for 'DTA_reports_partitionscheme'.
There are 0 rows in 0 pages for object "DTA_reports_partitionscheme".
DBCC results for 'sysdbmaintplans'.
There are 2 rows in 1 pages for object "sysdbmaintplans".
DBCC results for 'sysmail_profileaccount'.
There are 1 rows in 1 pages for object "sysmail_profileaccount".
DBCC results for 'MSdbms'.
There are 7 rows in 1 pages for object "MSdbms".
DBCC results for 'DTA_reports_table'.
There are 0 rows in 0 pages for object "DTA_reports_table".
DBCC results for 'MSdbms_datatype'.
There are 141 rows in 1 pages for object "MSdbms_datatype".
DBCC results for 'sysmail_servertype'.
There are 1 rows in 1 pages for object "sysmail_servertype".
DBCC results for 'DTA_reports_tableview'.
There are 0 rows in 0 pages for object "DTA_reports_tableview".
DBCC results for 'sysdbmaintplan_jobs'.
There are 3 rows in 1 pages for object "sysdbmaintplan_jobs".
DBCC results for 'MSdbms_map'.
There are 248 rows in 3 pages for object "MSdbms_map".
DBCC results for 'DTA_reports_query'.
There are 0 rows in 0 pages for object "DTA_reports_query".
DBCC results for 'sysdbmaintplan_databases'.
There are 1 rows in 1 pages for object "sysdbmaintplan_databases".
DBCC results for 'sysmail_server'.
There are 1 rows in 1 pages for object "sysmail_server".
DBCC results for 'DTA_reports_querytable'.
There are 0 rows in 0 pages for object "DTA_reports_querytable".
DBCC results for 'sysdbmaintplan_history'.
There are 1253 rows in 42 pages for object "sysdbmaintplan_history".
DBCC results for 'DTA_reports_querydatabase'.
There are 0 rows in 0 pages for object "DTA_reports_querydatabase".
DBCC results for 'DTA_reports_index'.
There are 0 rows in 0 pages for object "DTA_reports_index".
DBCC results for 'MSdbms_datatype_mapping'.
There are 325 rows in 3 pages for object "MSdbms_datatype_mapping".
DBCC results for 'sysmail_configuration'.
There are 7 rows in 1 pages for object "sysmail_configuration".
DBCC results for 'sysmail_mailitems'.
There are 20 rows in 7 pages for object "sysmail_mailitems".
DBCC results for 'DTA_reports_queryindex'.
There are 0 rows in 0 pages for object "DTA_reports_queryindex".
DBCC results for 'DTA_reports_column'.
There are 0 rows in 0 pages for object "DTA_reports_column".
DBCC results for 'log_shipping_primaries'.
There are 0 rows in 0 pages for object "log_shipping_primaries".
DBCC results for 'DTA_reports_indexcolumn'.
There are 0 rows in 0 pages for object "DTA_reports_indexcolumn".
DBCC results for 'log_shipping_secondaries'.
There are 0 rows in 0 pages for object "log_shipping_secondaries".
DBCC results for 'DTA_reports_querycolumn'.
There are 0 rows in 0 pages for object "DTA_reports_querycolumn".
DBCC results for 'sysmail_attachments'.
There are 0 rows in 0 pages for object "sysmail_attachments".
DBCC results for 'sysmail_send_retries'.
There are 0 rows in 0 pages for object "sysmail_send_retries".
DBCC results for 'backupmediaset'.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1858105660, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594047168512 (type In-row data). Page (1:1624) is missing a reference from previous page (1:1665). Possible chain linkage problem.
There are 1668 rows in 24 pages for object "backupmediaset".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediaset' (object ID 1858105660).
DBCC results for 'sysmail_log'.
There are 22 rows in 1 pages for object "sysmail_log".
DBCC results for 'backupmediafamily'.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1890105774, index ID 1, partition ID 72057594042908672, alloc unit ID 72057594047299584 (type In-row data). Page (1:1587) is missing a reference from previous page (1:1586). Possible chain linkage problem.
There are 1637 rows in 33 pages for object "backupmediafamily".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediafamily' (object ID 1890105774).
DBCC results for 'sysdtspackages90'.
There are 2 rows in 1 pages for object "sysdtspackages90".
DBCC results for 'backupset'.
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 41, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1604), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 42, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1605), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 43, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1606), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:662), slot 44, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1607), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1604) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1605) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1606) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1607) allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1609), whose header indicates that it is allocated to object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data). Page (1:1609) is missing a reference from previous page (1:593). Possible chain linkage problem.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data). Page (1:1632) is missing a reference from previous page (1:1607). Possible chain linkage problem.
There are 1629 rows in 118 pages for object "backupset".
CHECKDB found 0 allocation errors and 11 consistency errors in table 'backupset' (object ID 1954106002).
DBCC results for 'sysdtspackagefolders90'.
There are 2 rows in 1 pages for object "sysdtspackagefolders90".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'sysmail_query_transfer'.
There are 0 rows in 0 pages for object "sysmail_query_transfer".
DBCC results for 'backupfilegroup'.
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:692), slot 12, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), refers to page (1:1609), slot 0, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1609) allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1610) is missing a reference from previous page (1:1609). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1617), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1617) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1618), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1618) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1619), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1619) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1620), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1620) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1621), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1621) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1622), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1622) is missing a reference from previous page (1:597). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1623), whose header indicates that it is allocated to object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data). Page (1:1623) is missing a reference from previous page (1:597). Possible chain linkage problem.
There are 2066 rows in 39 pages for object "backupfilegroup".
CHECKDB found 0 allocation errors and 17 consistency errors in table 'backupfilegroup' (object ID 2002106173).
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'sysdtslog90'.
There are 0 rows in 0 pages for object "sysdtslog90".
DBCC results for 'sysmail_attachments_transfer'.
There are 0 rows in 0 pages for object "sysmail_attachments_transfer".
DBCC results for 'backupfile'.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1604), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1604) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1605), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1605) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1606), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1606) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1607), whose header indicates that it is allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), is allocated by another object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1607) is missing a reference from previous page (1:599). Possible chain linkage problem.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1617) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1618) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1619) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1620) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1621) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1622) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1623) allocated to object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:1640) is missing a reference from previous page (1:1623). Possible chain linkage problem.
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 68, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1617), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 69, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1618), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 70, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1619), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 71, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1620), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 72, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1621), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 73, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1622), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:1693), slot 74, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1623), slot 0, in object ID 2002106173, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047561728 (type In-row data).
There are 3677 rows in 205 pages for object "backupfile".
CHECKDB found 0 allocation errors and 23 consistency errors in table 'backupfile' (object ID 2050106344).
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'restorehistory'.
There are 7 rows in 1 pages for object "restorehistory".
DBCC results for 'sysproxies'.
There are 0 rows in 0 pages for object "sysproxies".
DBCC results for 'restorefile'.
There are 11 rows in 2 pages for object "restorefile".
CHECKDB found 0 allocation errors and 54 consistency errors in database 'msdb'.
repair_allow_data_loss 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.

Post #1379600
Posted Wednesday, October 31, 2012 9:53 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, June 10, 2013 3:10 AM
Points: 54, Visits: 255
Server team did the server refresh and I was coordinating from the database end.

Since there was some issue with index, I planned to restore the database. There is no issue on user database now. However, I am able to see 54 consistency errors on MSDB.

Thanks,
Dev.
Post #1379602
Posted Thursday, November 1, 2012 2:46 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:41 AM
Points: 42,827, Visits: 35,957
If you have a clean backup of MSDB, I would suggest you restore it. Otherwise repairing this will lose a fair bit of data in the backup history tables


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1379673
Posted Thursday, November 1, 2012 3:48 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, June 10, 2013 3:10 AM
Points: 54, Visits: 255
Hi,

I have a practice to backup the system databases. Shall i go ahead and restore the Oct 23rd backup, that is before the server refresh.

Could you please let me know the reason behind this error.

Thanks,
Dev.
Post #1379701
Posted Thursday, November 1, 2012 4:03 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:41 AM
Points: 42,827, Visits: 35,957
As I said, if you have a clean backup, I suggest you restore it.

As for the cause - IO subsystem problems of some form. That's what 99% of corruption is caused by.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1379709
Posted Thursday, November 1, 2012 4:25 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, June 10, 2013 3:10 AM
Points: 54, Visits: 255
I should take the SQL Server in single user mode for restoring the system databases. Could you please confirm
Post #1379716
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse