in recovery - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

in recovery

Author

Topic

b5white
Starting Member

18 Posts

Posted - 2011-05-25 : 18:10:41

I have a couple of databases that claim to be in recovery mode.
The CPU is at 0%.
I get loads of "non-yielding" messages (see the end of the log).
On the assumption that something isn't yielding, restarted
SQL Server.

Still just gives the "non-yielding" messages, now with the
addition of the core dump.

Suggestions? Next step?

------------------------
2011-05-25 16:50:08.01 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2011-05-25 16:50:08.01 Server (c) 2005 Microsoft Corporation.
2011-05-25 16:50:08.01 Server All rights reserved.
2011-05-25 16:50:08.01 Server Server process ID is 5904.
2011-05-25 16:50:08.01 Server Authentication mode is MIXED.
2011-05-25 16:50:08.01 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2011-05-25 16:50:08.01 Server This instance of SQL Server last reported using a process ID of 7976 at 5/25/2011 4:43:20 PM (local) 5/25/2011 9:43:20 PM (UTC). This is an informational message only; no user action is required.
2011-05-25 16:50:08.01 Server Registry startup parameters:
2011-05-25 16:50:08.01 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-05-25 16:50:08.01 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-05-25 16:50:08.01 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-05-25 16:50:08.02 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-05-25 16:50:08.02 Server Detected 2 CPUs. This is an informational message; no user action is required.
2011-05-25 16:50:08.07 Server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
2011-05-25 16:50:08.13 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-05-25 16:50:08.15 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2011-05-25 16:50:09.17 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2011-05-25 16:50:09.17 Server Database mirroring has been enabled on this instance of SQL Server.
2011-05-25 16:50:09.17 spid5s Starting up database 'master'.
2011-05-25 16:50:09.24 spid5s 5 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2011-05-25 16:50:09.26 spid5s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2011-05-25 16:50:09.28 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-05-25 16:50:09.34 spid5s SQL Trace ID 1 was started by login "sa".
2011-05-25 16:50:09.34 spid5s Starting up database 'mssqlsystemresource'.
2011-05-25 16:50:09.35 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2011-05-25 16:50:09.43 spid5s Server name is 'TSKINMUNDYCI'. This is an informational message only. No user action is required.
2011-05-25 16:50:09.43 spid9s Starting up database 'model'.
2011-05-25 16:50:09.78 Server A self-generated certificate was successfully loaded for encryption.
2011-05-25 16:50:09.79 Server Server is listening on [ 'any' <ipv4> 1433].
2011-05-25 16:50:09.79 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-05-25 16:50:09.79 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2011-05-25 16:50:09.79 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-05-25 16:50:09.79 Server Dedicated admin connection support was established for listening locally on port 1434.
2011-05-25 16:50:09.95 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-05-25 16:50:09.96 spid13s Starting up database 'msdb'.
2011-05-25 16:50:09.96 spid12s Starting up database 'CheckImaging'.
2011-05-25 16:50:09.96 spid14s Starting up database 'TellerAppClient'.
2011-05-25 16:50:09.96 spid15s Starting up database 'TellerAppMaster'.
2011-05-25 16:50:09.96 spid16s Starting up database 'CITemp'.
2011-05-25 16:50:10.07 spid9s Clearing tempdb database.
2011-05-25 16:50:10.54 spid12s Using 'dbghelp.dll' version '4.0.5'
2011-05-25 16:50:10.57 spid12s **Dump thread - spid = 12, PSS = 0x03E0C7D8, EC = 0x03E0C7E0
2011-05-25 16:50:10.57 spid12s ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0008.txt
2011-05-25 16:50:10.57 spid12s * *******************************************************************************
2011-05-25 16:50:10.57 spid12s *
2011-05-25 16:50:10.57 spid12s * BEGIN STACK DUMP:
2011-05-25 16:50:10.57 spid12s * 05/25/11 16:50:10 spid 12
2011-05-25 16:50:10.57 spid12s *
2011-05-25 16:50:10.57 spid12s * Location: "logmgr.cpp":5512
2011-05-25 16:50:10.57 spid12s * Expression: !(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)
2011-05-25 16:50:10.57 spid12s * SPID: 12
2011-05-25 16:50:10.57 spid12s * Process ID: 5904
2011-05-25 16:50:10.57 spid12s *
2011-05-25 16:50:10.57 spid12s *
2011-05-25 16:50:10.57 spid12s *
2011-05-25 16:50:10.57 spid12s * MODULE BASE END SIZE
2011-05-25 16:50:10.57 spid12s * sqlservr 01000000 02C09FFF 01c0a000
2011-05-25 16:50:10.57 spid12s * ntdll 7C800000 7C8BFFFF 000c0000
2011-05-25 16:50:10.57 spid12s * kernel32 77E40000 77F41FFF 00102000
2011-05-25 16:50:10.57 spid12s * MSVCR80 78130000 781CAFFF 0009b000
2011-05-25 16:50:10.57 spid12s * msvcrt 77BA0000 77BF9FFF 0005a000
2011-05-25 16:50:10.57 spid12s * MSVCP80 7C420000 7C4A6FFF 00087000
2011-05-25 16:50:10.57 spid12s * ADVAPI32 7D1E0000 7D27BFFF 0009c000
2011-05-25 16:50:10.57 spid12s * RPCRT4 77C50000 77CEFFFF 000a0000
2011-05-25 16:50:10.57 spid12s * Secur32 76F50000 76F62FFF 00013000
2011-05-25 16:50:10.57 spid12s * USER32 77380000 77410FFF 00091000
2011-05-25 16:50:10.57 spid12s * GDI32 77C00000 77C48FFF 00049000
2011-05-25 16:50:10.57 spid12s * CRYPT32 761B0000 76242FFF 00093000
2011-05-25 16:50:10.57 spid12s * MSASN1 76190000 761A1FFF 00012000
2011-05-25 16:50:10.57 spid12s * MSWSOCK 71B20000 71B60FFF 00041000
2011-05-25 16:50:10.57 spid12s * WS2_32 71C00000 71C16FFF 00017000
2011-05-25 16:50:10.57 spid12s * WS2HELP 71BF0000 71BF7FFF 00008000
2011-05-25 16:50:10.57 spid12s * USERENV 76920000 769E1FFF 000c2000
2011-05-25 16:50:10.57 spid12s * opends60 333E0000 333E6FFF 00007000
2011-05-25 16:50:10.57 spid12s * NETAPI32 71C40000 71C96FFF 00057000
2011-05-25 16:50:10.57 spid12s * SHELL32 7C8D0000 7D0CEFFF 007ff000
2011-05-25 16:50:10.57 spid12s * SHLWAPI 7D180000 7D1D1FFF 00052000
2011-05-25 16:50:10.57 spid12s * IMM32 76290000 762ACFFF 0001d000
2011-05-25 16:50:10.57 spid12s * comctl32 77420000 77522FFF 00103000
2011-05-25 16:50:10.57 spid12s * psapi 76B70000 76B7AFFF 0000b000
2011-05-25 16:50:10.57 spid12s * instapi 48060000 48069FFF 0000a000
2011-05-25 16:50:10.57 spid12s * sqlevn70 4F610000 4F7B8FFF 001a9000
2011-05-25 16:50:10.57 spid12s * SQLOS 344D0000 344D4FFF 00005000
2011-05-25 16:50:10.57 spid12s * rsaenh 68000000 68034FFF 00035000
2011-05-25 16:50:10.57 spid12s * AUTHZ 76C40000 76C53FFF 00014000
2011-05-25 16:50:10.57 spid12s * MSCOREE 34120000 34169FFF 0004a000
2011-05-25 16:50:10.57 spid12s * mscoreei 341C0000 34225FFF 00066000
2011-05-25 16:50:10.57 spid12s * ole32 77670000 777A8FFF 00139000
2011-05-25 16:50:10.57 spid12s * msv1_0 76C90000 76CB6FFF 00027000
2011-05-25 16:50:10.57 spid12s * cryptdll 766E0000 766EBFFF 0000c000
2011-05-25 16:50:10.57 spid12s * iphlpapi 76CF0000 76D09FFF 0001a000
2011-05-25 16:50:10.57 spid12s * kerberos 61C20000 61C78FFF 00059000
2011-05-25 16:50:10.57 spid12s * schannel 76750000 76777FFF 00028000
2011-05-25 16:50:10.57 spid12s * COMRES 77010000 770D5FFF 000c6000
2011-05-25 16:50:10.57 spid12s * XOLEHLP 61CD0000 61CD5FFF 00006000
2011-05-25 16:50:10.57 spid12s * MSDTCPRX 61CE0000 61D58FFF 00079000
2011-05-25 16:50:10.57 spid12s * OLEAUT32 77D00000 77D8AFFF 0008b000
2011-05-25 16:50:10.57 spid12s * msvcp60 61D60000 61DC4FFF 00065000
2011-05-25 16:50:10.57 spid12s * MTXCLU 61DD0000 61DE8FFF 00019000
2011-05-25 16:50:10.57 spid12s * VERSION 77B90000 77B97FFF 00008000
2011-05-25 16:50:10.57 spid12s * WSOCK32 71BB0000 71BB8FFF 00009000
2011-05-25 16:50:10.57 spid12s * CLUSAPI 61DF0000 61E01FFF 00012000
2011-05-25 16:50:10.57 spid12s * RESUTILS 61E10000 61E22FFF 00013000
2011-05-25 16:50:10.57 spid12s * DNSAPI 76ED0000 76EF9FFF 0002a000
2011-05-25 16:50:10.57 spid12s * winrnr 76F70000 76F76FFF 00007000
2011-05-25 16:50:10.57 spid12s * WLDAP32 76F10000 76F3DFFF 0002e000
2011-05-25 16:50:10.57 spid12s * rasadhlp 76F80000 76F84FFF 00005000
2011-05-25 16:50:10.57 spid12s * security 62260000 62263FFF 00004000
2011-05-25 16:50:10.57 spid12s * msfte 62890000 62AE8FFF 00259000
2011-05-25 16:50:10.57 spid12s * dbghelp 62AF0000 62C04FFF 00115000
2011-05-25 16:50:10.57 spid12s * WINTRUST 76BB0000 76BDBFFF 0002c000
2011-05-25 16:50:10.57 spid12s * imagehlp 76C10000 76C37FFF 00028000
2011-05-25 16:50:10.57 spid12s * dssenh 68100000 68126FFF 00027000
2011-05-25 16:50:10.57 spid12s * hnetcfg 62E60000 62EB9FFF 0005a000
2011-05-25 16:50:10.57 spid12s * wshtcpip 71AE0000 71AE7FFF 00008000
2011-05-25 16:50:10.57 spid12s * NTMARTA 77E00000 77E20FFF 00021000
2011-05-25 16:50:10.57 spid12s * SAMLIB 7E020000 7E02EFFF 0000f000
2011-05-25 16:50:10.57 spid12s * ntdsapi 766F0000 76703FFF 00014000
2011-05-25 16:50:10.57 spid12s * xpsp2res 62F00000 631C4FFF 002c5000
2011-05-25 16:50:10.57 spid12s * CLBCatQ 777B0000 77832FFF 00083000
2011-05-25 16:50:10.57 spid12s * sqlncli 631D0000 633F3FFF 00224000
2011-05-25 16:50:10.57 spid12s * COMCTL32 77530000 775C6FFF 00097000
2011-05-25 16:50:10.57 spid12s * comdlg32 762B0000 762F8FFF 00049000
2011-05-25 16:50:10.57 spid12s * SQLNCLIR 007C0000 007F2FFF 00033000
2011-05-25 16:50:10.57 spid12s * msftepxy 63500000 63514FFF 00015000
2011-05-25 16:50:10.57 spid12s * dbghelp 63960000 63A74FFF 00115000
2011-05-25 16:50:10.57 spid12s *
2011-05-25 16:50:10.57 spid12s * Edi: 627CCA18: 001428A8 00000000 00000000 00000000 00000000 00000000
2011-05-25 16:50:10.57 spid12s * Esi: 00000000:
2011-05-25 16:50:10.57 spid12s * Eax: 627CC8FC: 000042AC 00000000 00000000 77E4BEF7 00000000 7C821B34
2011-05-25 16:50:10.57 spid12s * Ebx: 0000003F:
2011-05-25 16:50:10.57 spid12s * Ecx: 627CCF6C: 00000000 00010007 00000000 0090008E 001428AC 627CC92C
2011-05-25 16:50:10.57 spid12s * Edx: 0000003D:
2011-05-25 16:50:10.57 spid12s * Eip: 77E4BEF7: 10C2C95E 01093D00 840FC000 00000095 F29DE950 9090FFFF
2011-05-25 16:50:10.57 spid12s * Ebp: 627CC94C: 627CC990 021A29C4 000042AC 00000000 00000000 00000000
2011-05-25 16:50:10.57 spid12s * SegCs: 7813001B: 00000000 00000000 00000000 00000000 00000000 00000000
2011-05-25 16:50:10.57 spid12s * EFlags: 00000246:
2011-05-25 16:50:10.57 spid12s * Esp: 627CC8F8: 03E0C7D8 000042AC 00000000 00000000 77E4BEF7 00000000
2011-05-25 16:50:10.57 spid12s * SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000 00000000
2011-05-25 16:50:10.57 spid12s * *******************************************************************************
2011-05-25 16:50:10.57 spid12s * -------------------------------------------------------------------------------
2011-05-25 16:50:10.57 spid12s * Short Stack Dump
2011-05-25 16:50:10.57 spid12s 77E4BEF7 Module(kernel32+0000BEF7)
2011-05-25 16:50:10.57 spid12s 021A29C4 Module(sqlservr+011A29C4)
2011-05-25 16:50:10.57 spid12s 021A6880 Module(sqlservr+011A6880)
2011-05-25 16:50:10.57 spid12s 020456BA Module(sqlservr+010456BA)
2011-05-25 16:50:10.57 spid12s 015A803C Module(sqlservr+005A803C)
2011-05-25 16:50:10.57 spid12s 010AA165 Module(sqlservr+000AA165)
2011-05-25 16:50:10.57 spid12s 021C4C9A Module(sqlservr+011C4C9A)
2011-05-25 16:50:10.57 spid12s 021D4A9F Module(sqlservr+011D4A9F)
2011-05-25 16:50:10.57 spid12s 020FD621 Module(sqlservr+010FD621)
2011-05-25 16:50:10.57 spid12s 020E97AF Module(sqlservr+010E97AF)
2011-05-25 16:50:10.57 spid12s 020F385C Module(sqlservr+010F385C)
2011-05-25 16:50:10.57 spid12s 020F342B Module(sqlservr+010F342B)
2011-05-25 16:50:10.57 spid12s 010077A6 Module(sqlservr+000077A6)
2011-05-25 16:50:10.57 spid12s 010078CC Module(sqlservr+000078CC)
2011-05-25 16:50:10.57 spid12s 010075DC Module(sqlservr+000075DC)
2011-05-25 16:50:10.57 spid12s 010B94A5 Module(sqlservr+000B94A5)
2011-05-25 16:50:10.57 spid12s 010B939C Module(sqlservr+000B939C)
2011-05-25 16:50:10.57 spid12s 010B9064 Module(sqlservr+000B9064)
2011-05-25 16:50:10.59 spid12s 010B9201 Module(sqlservr+000B9201)
2011-05-25 16:50:10.59 spid12s 781329BB Module(MSVCR80+000029BB)
2011-05-25 16:50:10.59 spid12s 78132A47 Module(MSVCR80+00002A47)
2011-05-25 16:50:10.59 spid12s Stack Signature for the dump is 0x1A5465A8
2011-05-25 16:50:10.99 spid12s External dump process return code 0x20000001.
External dump process returned no errors.

2011-05-25 16:50:10.99 spid12s Error: 17066, Severity: 16, State: 1.
2011-05-25 16:50:10.99 spid12s SQL Server Assertion: File: <"logmgr.cpp">, line=5512 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2011-05-25 16:50:10.99 spid12s Error: 3624, Severity: 20, State: 1.
2011-05-25 16:50:10.99 spid12s A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
2011-05-25 16:50:11.79 spid9s Starting up database 'tempdb'.
2011-05-25 16:50:11.99 spid13s The Service Broker protocol transport is disabled or not configured.
2011-05-25 16:50:11.99 spid13s The Database Mirroring protocol transport is disabled or not configured.
2011-05-25 16:50:12.01 spid13s Service Broker manager has started.
2011-05-25 16:51:33.15 Server Using 'dbghelp.dll' version '4.0.5'
2011-05-25 16:51:33.15 Server ***Unable to get thread context - no pss
2011-05-25 16:51:33.15 Server * *******************************************************************************
2011-05-25 16:51:33.15 Server *
2011-05-25 16:51:33.15 Server * BEGIN STACK DUMP:
2011-05-25 16:51:33.15 Server * 05/25/11 16:51:33 spid 0
2011-05-25 16:51:33.15 Server *
2011-05-25 16:51:33.15 Server * Non-yielding Scheduler
2011-05-25 16:51:33.15 Server *
2011-05-25 16:51:33.15 Server * *******************************************************************************
2011-05-25 16:51:33.15 Server Stack Signature for the dump is 0x00000065
2011-05-25 16:51:33.43 Server External dump process return code 0x20000001.
External dump process returned no errors.

2011-05-25 16:51:33.43 Server Process 12:0:0 (0x118c) Worker 0x03DFC0E8 appears to be non-yielding on Scheduler 1. Thread creation time: 12950833809342. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 74998 ms.
2011-05-25 16:52:33.43 Server Process 12:0:0 (0x118c) Worker 0x03DFC0E8 appears to be non-yielding on Scheduler 1. Thread creation time: 12950833809342. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 135277 ms.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-05-25 : 18:41:31

How long are you waiting before you restart SQL Server? Crash recovery can take a while if you have a lot of VLF's. Any idea how many you have on the problematic database? 500+ is bad, something in the thousands is very bad. We had a system with 80,000+ VLF's due to a SQL Server bug (4GB bug), and it took 30 minutes to complete crash recovery of it after a restart. Once we fixed the VLF's, crash recovery took just seconds.

Those stack dumps are not good. You appear to be out of date on your build number for SQL. You should really consider installing service pack 4 plus whatever the latest hotfix is.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

b5white
Starting Member

18 Posts

Posted - 2011-05-25 : 18:56:03

Searching on the exact error led us to SP 4.
Installing as we speak.

Thanks,
Brad.

b5white
Starting Member

18 Posts

Posted - 2011-05-25 : 21:00:05

The upgrade failed with the below message.
I put the database in emergency mode and detached it.
Then the update succeeded.

05/25/2011 19:14:31.920 MSP Error: 29536 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The log scan number (36116:334:1) passed to log scan in database 'CheckImaging' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. . To continue, correct the problem, and then run SQL Server Setup again.
05/25/2011 19:14:31.998 MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The log scan number (36116:334:1) passed to log scan in database 'CheckImaging' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. . To continue, correct the problem, and then run SQL Server Setup again.
05/25/2011 19:14:40.545 MSP returned 1603: A fatal error occurred during installation.
05/25/2011 19:14:40.873 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
05/25/2011 19:14:40.904 Registry: Cannot read registry key value "Debug", error 0
05/25/2011 19:14:41.482 Copy Engine: Error, unable to install MSP file: c:\d7f819a8c9caaefa83738b092d2bb50a\HotFixSQL\Files\sqlrun_sql.msp
05/25/2011 19:14:41.529 The following exception occurred: Unable to install Windows Installer MSP file Date: 05/25/2011 19:14:41.529 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
05/25/2011 19:14:48.935 Watson: Param1 = repl_hotfix_install.sql

b5white
Starting Member

18 Posts

Posted - 2011-05-25 : 21:02:02

Trying to attach the database after the update gives a similar error.

I'm not clear on how to run the DBCC it suggests if we can't
attach the database.

Thanks!

SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:4089856; actual 29545:1750338061). It occurred during a read of page (1:4089856) in database ID 5 at offset 0x000007cd000000 in file 'C:\Data\Checkimaging.mdf'. 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.
Could not open new database 'Checkimaging'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 824)

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-05-25 : 23:00:01

Do you have backups of this database? I sure hope so. You never answered my question about how long you waited for the "in recovery" message to clear before you did the restart.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-05-26 : 06:46:55

Restore from backup.

You should never, never detach a suspect database as they won't re-attach.

--
Gail Shaw
SQL Server MVP

b5white
Starting Member

18 Posts

Posted - 2011-05-26 : 09:58:12

> restore from backup
That was we told them at first too, but none of the backup
would restore cleanly, so we are trying to tease as much
data out of the most current as we can.
If this is hopeless, then we can go back to the most recent
backup and start over.
I don't want to do that until we've completely given up on this one.

> how long did you leave it in restore mode?
It was kicking out the "unyielding" message about once every
minute and there were about 30 of the messages. So 30 minutes
seems like a safe guess. With 0% cpu. Is there a better way
to clear the "unyileding" condition?

> never detach a suspect DB.
We'll keep that in mind for next time.

Does the "create a new db, take the server down, slip the old
files in place" trick work in this case?

We continue to train, plead, and cajole as much as we can
to keep an eye on their backups, but ultimately they are
responsible and we can't force them to do anything until
it gets to this point and they call us for help.
We've started to include reminders/horror stories in our
weekly newsletter, but...

Thanks,
Brad.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-05-26 : 10:20:55

quote:
Originally posted by b5white

Does the "create a new db, take the server down, slip the old
files in place" trick work in this case?

Yes. The DBs will likely come up suspect. Take them into Emergency Mode, run the following, post the results.


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

--
Gail Shaw
SQL Server MVP

b5white
Starting Member

18 Posts

Posted - 2011-05-26 : 11:18:11

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 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3922680) to (1:3930767). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3930768) to (1:3938855). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3938856) to (1:3946943). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3946944) to (1:3955031). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3955032) to (1:3963119). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3963120) to (1:3971207). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3971208) to (1:3979295). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3979296) to (1:3987383). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3987384) to (1:3995471). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:3995472) to (1:4003559). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4003560) to (1:4011647). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4011648) to (1:4019735). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4019736) to (1:4027823). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4027824) to (1:4035911). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4035912) to (1:4043999). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4044000) to (1:4052087). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4052088) to (1:4060175). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4060176) to (1:4068263). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4068264) to (1:4076351). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4076352) to (1:4084439). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4084440) to (1:4092527). See other errors for cause.
Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4084440) to (1:4602071). See other errors for cause.
Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4084440) to (1:4602071). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4092528) to (1:4100615). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4100616) to (1:4108703). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4108704) to (1:4116791). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4116792) to (1:4124879). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4124880) to (1:4132967). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4132968) to (1:4141055). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4141056) to (1:4149143). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4149144) to (1:4157231). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4157232) to (1:4165319). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4165320) to (1:4173407). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4173408) to (1:4181495). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4181496) to (1:4189583). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4189584) to (1:4197671). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4197672) to (1:4205759). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4205760) to (1:4213847). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4213848) to (1:4221935). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4221936) to (1:4230023). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4230024) to (1:4238111). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4238112) to (1:4246199). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4246200) to (1:4254287). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4254288) to (1:4262375). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4262376) to (1:4270463). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4270464) to (1:4278551). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4278552) to (1:4286639). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4286640) to (1:4294727). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4294728) to (1:4302815). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4302816) to (1:4310903). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4310904) to (1:4318991). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4318992) to (1:4327079). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4327080) to (1:4335167). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4335168) to (1:4343255). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4343256) to (1:4351343). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4351344) to (1:4359431). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4359432) to (1:4367519). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4367520) to (1:4375607). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4375608) to (1:4383695). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4383696) to (1:4391783). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4391784) to (1:4399871). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4399872) to (1:4407959). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4407960) to (1:4416047). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4416048) to (1:4424135). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4424136) to (1:4432223). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4432224) to (1:4440311). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4440312) to (1:4448399). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4448400) to (1:4456487). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4456488) to (1:4464575). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:4464576) to (1:4472663). See other errors for cause.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 2315167010111553536 (type Unknown), page (8307:1763734377). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -1.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7021218953279242240 (type Unknown), page ID (1:4089862) contains an incorrect page ID in its page header. The PageId in the page header = (2573:539042151).
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7517748388143366144 (type Unknown), page (25700:1634738291). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -4.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3922680) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3930768) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3938856) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3946944) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3955032) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3963120) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3971208) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3979296) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3987384) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:3995472) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4003560) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4011648) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4019736) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4027824) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4035912) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4044000) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4052088) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4060176) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4068264) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4076352) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4084440) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4089856) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4092528) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4100616) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4108704) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4116792) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4124880) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4132968) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4141056) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4149144) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4157232) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4165320) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4173408) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4181496) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4189584) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4197672) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4205760) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4213848) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4221936) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4230024) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4238112) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4246200) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4254288) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4262376) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4270464) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4278552) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4286640) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4294728) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4302816) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4310904) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4318992) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4327080) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4335168) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4343256) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4351344) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4359432) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4367520) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4375608) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4383696) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4391784) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4399872) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4407960) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4416048) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4424136) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4432224) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4440312) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4448400) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4456488) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7956011615661588480 (type Unknown), page ID (1:4464576) contains an incorrect page ID in its page header. The PageId in the page header = (29545:1750338061).
CHECKDB found 142 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 142 allocation errors and 0 consistency errors in database 'CheckImaging'.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:4119200; actual 29545:1750338061). It occurred during a read of page (1:4119200) in database ID 5 at offset 0x000007db540000 in file 'C:\DATA\CheckImaging.mdf'. 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.

b5white
Starting Member

18 Posts

Posted - 2011-05-26 : 11:28:10

It just said "CHECKDB" with no recovery level,
which I thought we just did.

They wanted to try repair with no data loss.
to do that we have to put it on single user mode.

I expected that to be a quick query, but it has been
going for a while.
I'm having them check the error log, meanwhile how
long should they let that run?

Thanks,
Brad.

UPDATE: No errors in the error log. Just
Setting database option SINGLE_USER to ON for database CheckImaging.

b5white
Starting Member

18 Posts

Posted - 2011-05-26 : 11:56:48

Finally got past the single user mode.

DBCC CHECKDB (checkimaging, REPAIR_REBUILD) WITH NO_INFOMSGS

Msg 7901, Level 16, State 1, Line 1
The repair statement was not processed. This level of repair is not supported when the database is in emergency mode.

Next Step?
Take it out of Emergency Mode and try the repair again?

Thanks,
Brad.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-05-26 : 14:42:38

The DB is irreparable. The errors to the allocation pages and system tables prevent check, much less repair. Restore from last good backup.

Repair rebuild, as the error clearly states, cannot be run on a DB in emergency mode. Only checkDB with repair_allow_data loss can be run. It'll fail, because of all the allocation errors. You cannot take the DB out of emergency mode without repairing it and, since repair will fail, there is pretty much nothing more you can do here.

P.s. whether the repair is run with data loss or not is not up to the users. It depends on the degree of damage. If repair allow data loss is required, a repair rebuild will not be able to fix the problem.

--
Gail Shaw
SQL Server MVP

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-05-26 : 14:52:56

p.p.s I would, at this point, do some intensive investigation of the IO subsystem on this server. Something has garbled what looks like a 4 GB chunk of the data file

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources