SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 logical consistency-based I/O error: torn page
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

zaty2405
Yak Posting Veteran

58 Posts

Posted - 08/01/2011 :  06:04:21  Show Profile  Reply with Quote
Hi,

Sql log keep on throwing the following error :

" SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x55555556). It occurred during a read of page (1:470922) in database ID 8 at offset 0x000000e5f14000 in file 'E:\DATA\SQL\SG0\Data\PROD.mdf:MSSQL_DBCC8'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online."

I run DBCC checkdb on PROD database but encountered the following :

" Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x55555556). It occurred during a read of page (1:470922) in database ID 8 at offset 0x000000e5f14000 in file 'E:\DATA\SQL\SG0\Data\PROD.mdf:MSSQL_DBCC8'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. "

I have checked and tempdb is running fine

Appreciate any help

THank you
zaty

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 08/01/2011 :  09:37:18  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Restore from backup.

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

zaty2405
Yak Posting Veteran

58 Posts

Posted - 08/01/2011 :  22:14:24  Show Profile  Reply with Quote
Hi Gail,

THanks for the reply.

I also run DBCC CHECKDB on MSDB database on this instance and received following error:

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 1444 rows in 12 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 209 rows in 2 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 243 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 1444 rows in 11 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 209 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 243 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 23 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 291 rows in 3 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 623 rows in 13 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 2724 rows in 63 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 370 rows in 7 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 524 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'.
Msg 2515, Level 16, State 1, Line 1
The page (1:349), object ID 60, index ID 1, partition ID 281474980642816, allocation unit ID 281474980642816 (type In-row data) has been modified, but is not marked as modified in the differential backup bitmap.
Msg 8929, Level 16, State 1, Line 1
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1922433024 owned by data record identified by RID = (1:349:0)
Msg 8961, Level 16, State 2, Line 1
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:45), slot 3, text ID 1922433024 does not match its reference from page (1:349), slot 0.
There are 788 rows in 250 pages for object "sys.sysobjvalues".
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sys.sysobjvalues' (object ID 60).
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 274 rows in 2 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 2419 rows in 18 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 354 rows in 22 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 0 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 14 rows in 2 pages for object "suspect_pages".
DBCC results for 'sysdownloadlist'.
There are 0 rows in 0 pages for object "sysdownloadlist".
DBCC results for 'sysjobhistory'.
Msg 8926, Level 16, State 3, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0 in object 117575457, index 1, partition 72057594039369728, AU 72057594043367424 (In-row data), and page (1:920)->next in object 2050106344, index 1, partition 72057594043236352, AU 72057594047627264 (In-row data), refer to page (1:1044) but are not in the same object.
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:806) is missing a reference from previous page (1:852). Possible chain linkage problem.
Msg 8935, 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). The previous link (1:773) on page (1:851) does not match the previous page (1:853) that the parent (1:746), slot 40 expects for this page.
Msg 8936, 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). B-tree chain linkage mismatch. (1:853)->next = (1:851), but (1:851)->Prev = (1:773).
Msg 8928, Level 16, State 1, Line 1
Object ID 117575457, index ID 1, partition ID 72057594039369728, alloc unit ID 72057594043367424 (type In-row data): Page (1:852) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 117575457, index ID 1, partition ID 72057594039369728, alloc unit ID 72057594043367424 (type In-row data), page (1:852). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8976, 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:852) was not seen in the scan although its parent (1:746) and previous (1:771) refer to it. Check any previous errors.
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:970) is missing a reference from previous page (1:851). Possible chain linkage problem.
Msg 2534, Level 16, State 1, Line 1
Table error: page (1:1044), whose header indicates that it is allocated to object ID 117575457, index ID 1, partition ID 72057594039369728, alloc unit ID 72057594043367424 (type In-row data), is allocated by another object.
Msg 8936, 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). B-tree chain linkage mismatch. (1:920)->next = (1:1044), but (1:1044)->Prev = (1:1165).
Msg 8981, 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). The next pointer of (1:1044) refers to page (1:1290). Neither (1:1290) nor its parent were encountered. Possible bad chain linkage.
There are 661 rows in 127 pages for object "sysjobhistory".
CHECKDB found 0 allocation errors and 11 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 4 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 4 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 24 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 90 rows in 2 pages for object "sysjobactivity".
DBCC results for 'sysjobsteps'.
There are 21 rows in 3 pages for object "sysjobsteps".
DBCC results for 'sysjobstepslogs'.
There are 0 rows in 0 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 4 rows in 1 pages for object "sysschedules".
DBCC results for 'MSdbms'.
There are 7 rows in 1 pages for object "MSdbms".
DBCC results for 'MSdbms_datatype'.
There are 141 rows in 1 pages for object "MSdbms_datatype".
DBCC results for 'sysdtstasklog'.
There are 0 rows in 0 pages for object "sysdtstasklog".
DBCC results for 'MSdbms_map'.
There are 248 rows in 3 pages for object "MSdbms_map".
DBCC results for 'sysjobschedules'.
There are 4 rows in 1 pages for object "sysjobschedules".
DBCC results for 'syscategories'.
There are 23 rows in 1 pages for object "syscategories".
DBCC results for 'sys.queue_messages_704721563'.
There are 0 rows in 1 pages for object "sys.queue_messages_704721563".
DBCC results for 'systargetservers'.
There are 0 rows in 0 pages for object "systargetservers".
DBCC results for 'sys.queue_messages_736721677'.
There are 0 rows in 1 pages for object "sys.queue_messages_736721677".
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 'MSdbms_datatype_mapping'.
There are 325 rows in 3 pages for object "MSdbms_datatype_mapping".
DBCC results for 'sysmaintplan_subplans'.
There are 0 rows in 0 pages for object "sysmaintplan_subplans".
DBCC results for 'sysmail_principalprofile'.
There are 1 rows in 1 pages for object "sysmail_principalprofile".
DBCC results for 'sysmaintplan_log'.
There are 0 rows in 0 pages for object "sysmaintplan_log".
DBCC results for 'sysmaintplan_logdetail'.
There are 0 rows in 0 pages for object "sysmaintplan_logdetail".
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 0 rows in 1 pages for object "syscachedcredentials".
DBCC results for 'sysdbmaintplans'.
There are 1 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 'sysmail_servertype'.
There are 1 rows in 1 pages for object "sysmail_servertype".
DBCC results for 'sysdbmaintplan_jobs'.
There are 0 rows in 0 pages for object "sysdbmaintplan_jobs".
DBCC results for 'sysdbmaintplan_databases'.
There are 0 rows in 0 pages for object "sysdbmaintplan_databases".
DBCC results for 'sysmail_server'.
There are 1 rows in 1 pages for object "sysmail_server".
DBCC results for 'sysdbmaintplan_history'.
There are 10806 rows in 359 pages for object "sysdbmaintplan_history".
DBCC results for 'sysmail_configuration'.
There are 7 rows in 1 pages for object "sysmail_configuration".
DBCC results for 'sysmail_mailitems'.
There are 1 rows in 1 pages for object "sysmail_mailitems".
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 'sysmail_attachments'.
There are 0 rows in 0 pages for object "sysmail_attachments".
DBCC results for 'sysmail_send_retries'.
There are 1 rows in 1 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:789) is missing a reference from previous page (1:730). Possible chain linkage problem.
There are 420 rows in 7 pages for object "backupmediaset".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediaset' (object ID 1858105660).
DBCC results for 'sysmail_query_transfer'.
There are 0 rows in 0 pages for object "sysmail_query_transfer".
DBCC results for 'sysmail_log'.
There are 3 rows in 1 pages for object "sysmail_log".
DBCC results for 'backupmediafamily'.
Msg 8936, 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). B-tree chain linkage mismatch. (1:734)->next = (1:922), but (1:922)->Prev = (1:924).
Msg 8928, Level 16, State 1, Line 1
Object ID 1890105774, index ID 1, partition ID 72057594042908672, alloc unit ID 72057594047299584 (type In-row data): Page (1:924) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1890105774, index ID 1, partition ID 72057594042908672, alloc unit ID 72057594047299584 (type In-row data), page (1:924). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8976, 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:924) was not seen in the scan although its parent (1:791) and previous (1:1036) refer to it. Check any previous errors.
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:1036) is missing a reference from previous page (1:734). Possible chain linkage problem.
Msg 8910, Level 16, State 1, Line 1
Page (1:1275) in database ID 4 is allocated to both object ID 1890105774, index ID 1, partition ID 72057594042908672, alloc unit ID 72057594047299584 (type In-row data), and object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data).
There are 382 rows in 12 pages for object "backupmediafamily".
CHECKDB found 1 allocation errors and 5 consistency errors in table 'backupmediafamily' (object ID 1890105774).
DBCC results for 'sysdtspackages90'.
There are 0 rows in 0 pages for object "sysdtspackages90".
DBCC results for 'sysmail_attachments_transfer'.
There are 0 rows in 0 pages for object "sysmail_attachments_transfer".
DBCC results for 'backupset'.
Msg 8906, Level 16, State 1, Line 1
Page (1:748) in database ID 4 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Msg 8980, 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). Index node page (1:766), slot 5 refers to child page (1:748) and previous child (1:1272), but they were not encountered.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:862) 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 8910, Level 16, State 1, Line 1
Page (1:862) in database ID 4 is allocated to both object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), and object ID 117575457, index ID 1, partition ID 72057594039369728, alloc unit ID 72057594043367424 (type In-row data).
Msg 8928, Level 16, State 1, Line 1
Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data): Page (1:882) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), page (1:882). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8980, 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). Index node page (1:766), slot 1 refers to child page (1:882) and previous child (1:738), but they were not encountered.
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:1008) is missing a reference from previous page (1:882). Possible chain linkage problem.
Msg 8906, Level 16, State 1, Line 1
Page (1:1272) in database ID 4 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Msg 8976, 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:1272) was not seen in the scan although its parent (1:766) and previous (1:811) refer to it. Check any previous errors.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1275) 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 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:1392) is missing a reference from previous page (1:748). Possible chain linkage problem.
There are 380 rows in 25 pages for object "backupset".
CHECKDB found 3 allocation errors and 9 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 'backupfilegroup'.
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:829) is missing a reference from previous page (1:742). Possible chain linkage problem.
There are 420 rows in 8 pages for object "backupfilegroup".
CHECKDB found 0 allocation errors and 1 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 'backupfile'.
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:761) is missing a reference from previous page (1:1044). Possible chain linkage problem.
Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:762), slot 2, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data), refers to page (1:1044), slot 0, in object ID 117575457, index ID 1, partition ID 72057594039369728, alloc unit ID 72057594043367424 (type In-row data).
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:920) is missing a reference from previous page (1:744). Possible chain linkage problem.
Msg 8934, Level 16, State 2, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). The high key value on page (1:1024) (level 0) is not less than the low key value in the parent (1:762), slot 7 of the next page (1:1025).
Msg 8934, Level 16, State 3, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). The high key value on page (1:1024) (level 0) is not less than the low key value in the parent (1:762), slot 7 of the next page (1:1025).
Msg 8935, 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). The previous link (1:744) on page (1:1026) does not match the previous page (1:1025) that the parent (1:762), slot 8 expects for this page.
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:1026) is missing a reference from previous page (1:744). Possible chain linkage problem.
Msg 8935, 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). The previous link (1:744) on page (1:1027) does not match the previous page (1:1026) that the parent (1:762), slot 9 expects for this page.
Msg 8934, Level 16, State 2, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). The high key value on page (1:1042) (level 0) is not less than the low key value in the parent (1:762), slot 6 of the next page (1:1024).
Msg 8934, Level 16, State 3, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). The high key value on page (1:1042) (level 0) is not less than the low key value in the parent (1:762), slot 6 of the next page (1:1024).
Msg 8935, 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). The previous link (1:761) on page (1:1042) does not match the previous page (1:861) that the parent (1:762), slot 5 expects for this page.
Msg 8936, 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). B-tree chain linkage mismatch. (1:861)->next = (1:1042), but (1:1042)->Prev = (1:761).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:1044) 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.
There are 774 rows in 38 pages for object "backupfile".
CHECKDB found 0 allocation errors and 13 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 0 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 0 rows in 1 pages for object "restorefile".
CHECKDB found 4 allocation errors and 43 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.


My question is should we restore MSDB database or we need to restore both MSDB and PROD database.

Thank you
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 08/02/2011 :  05:37:06  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Well your initial CheckDB results were from the PROD database. Based on the new set, looks like you need to restore both.

Something's done some real damage to the databases on this instance. Check your hardware, specifically the IO subsystem.

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

zaty2405
Yak Posting Veteran

58 Posts

Posted - 08/04/2011 :  02:27:02  Show Profile  Reply with Quote
Hi Gail,

I have no backup file available to restore from.

Any idea how to save this database ?

Here is the output from DBCC CHECKDB (PROD)

Msg 8946, Level 16, State 12, Line 1
Table error: Allocation page (1:598512) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590504) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590512) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590520) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590528) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590536) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590544) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590560) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590568) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590576) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590584) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590592) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590600) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590608) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590616) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590624) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590632) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590640) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590648) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590656) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590680) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590688) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590696) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590704) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590712) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590720) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590728) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590736) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590744) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590768) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590776) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590784) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590792) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590800) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590808) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590824) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590832) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590840) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590856) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590864) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590872) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590880) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590888) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590904) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590912) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590920) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590928) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590936) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590944) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590952) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590960) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590968) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590976) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590984) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:590992) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591000) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591016) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591032) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591040) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591048) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591056) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591064) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591072) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591088) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591112) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591120) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591128) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591136) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591144) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591152) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591160) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591168) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591176) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591184) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591192) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591200) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591208) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591216) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591224) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591232) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591240) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591256) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591264) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591272) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591280) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591288) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591296) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591304) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591312) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591320) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591328) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591336) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591344) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591352) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591360) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591368) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591376) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591384) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591392) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591400) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591408) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591416) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591424) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591432) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591440) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591448) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591456) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591464) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591472) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591480) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591488) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591496) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591504) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591512) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591520) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591528) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591536) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591544) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591552) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591560) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591568) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591576) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591584) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591600) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591608) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591616) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591624) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591632) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591640) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591648) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591656) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8905, Level 16, State 1, Line 1
Extent (1:591664) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Msg 8966, Level 16, State 4, Line 1
Unable to read and latch page (1:598512) with latch type SH. UtilDbccVerifyPageId failed.
CHECKDB found 131 allocation errors and 1 consistency errors not associated with any single object.
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:599624) in object ID 165575628, index ID 2, partition ID 573801117777920, alloc unit ID 573801117777920 (type In-row data) is beyond the range of this database.
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:598688) in object ID 165575628, index ID 3, partition ID 855276094488576, alloc unit ID 855276094488576 (type In-row data) is beyond the range of this database.
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:599616) in object ID 165575628, index ID 4, partition ID 1136751071199232, alloc unit ID 1136751071199232 (type In-row data) is beyond the range of this database.
CHECKDB found 3 allocation errors and 0 consistency errors in table 'tbDeployment' (object ID 165575628).
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:599232) in object ID 917578307, index ID 1, partition ID 341609388638208, alloc unit ID 341609388638208 (type In-row data) is beyond the range of this database.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'tbPrerequisite' (object ID 917578307).
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:598976) in object ID 1221579390, index ID 1, partition ID 361532403613696, alloc unit ID 361532403613696 (type In-row data) is beyond the range of this database.
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:599544) in object ID 1221579390, index ID 1, partition ID 361532403613696, alloc unit ID 361532403613696 (type In-row data) is beyond the range of this database.
CHECKDB found 2 allocation errors and 0 consistency errors in table 'tbFile' (object ID 1221579390).
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:599600) in object ID 1285579618, index ID 1, partition ID 365726722555904, alloc unit ID 365726722555904 (type In-row data) is beyond the range of this database.
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:599744) in object ID 1285579618, index ID 3, partition ID 928676675977216, alloc unit ID 928676675977216 (type In-row data) is beyond the range of this database.
CHECKDB found 2 allocation errors and 0 consistency errors in table 'tbXml' (object ID 1285579618).
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:599760) in object ID 1413580074, index ID 2, partition ID 655590337150976, alloc unit ID 655590337150976 (type In-row data) is beyond the range of this database.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'tbFileOnServer' (object ID 1413580074).
Msg 2579, Level 16, State 1, Line 1
Table error: Extent (1:598848) in object ID 2130106629, index ID 2, partition ID 702548621459456, alloc unit ID 702548621459456 (type In-row data) is beyond the range of this database.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'tbPreComputedLocalizedProperty' (object ID 2130106629).
CHECKDB found 141 allocation errors and 1 consistency errors in database 'PROD'.


Thanks
Zaty
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 08/04/2011 :  04:48:51  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
That's not repairable in any way.

Script all objects, some will probably fail
Export all data, some will likely fail
Recreate the database from scratch.

Why oh why do you not have a backup????

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

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 08/04/2011 :  04:50:24  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Oh, you also need to look at the IO subsystem on that server. Looks like it has severe problems.

--
Gail Shaw
SQL Server MVP
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.38 seconds. Powered By: Snitz Forums 2000