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
 SQL Fatal Error

Author  Topic 

tunterberger
Starting Member

2 Posts
Posted - 2008-06-22 : 23:35:58
Here is the SQLDump log from our system. This database has not been backed up for a long time and a recent backup attempt failed. Without a recent backup, what would you advise our next step be?

=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 9.00.3054.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.


Computer type is AT/AT COMPATIBLE.
Bios Version is INTEL - 20030825
BIOS Date: 08/25/03 14:08:08 Ver: 08.00.09
Current time is 14:38:58 06/20/08.
1 Intel x86 level 15, 3 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.

Memory
MemoryLoad = 69%
Total Physical = 3054 MB
Available Physical = 929 MB
Total Page File = 4416 MB
Available Page File = 2393 MB
Total Virtual = 2047 MB
Available Virtual = 322 MB


DBCC RESULTS
--------------------
<DbccResults>
<Dbcc ID="0" Error="8966" Severity="16" State="2">Unable to read and latch page (1:258137) with latch type SH. 23
(Data error (cyclic redundancy check).) failed. </Dbcc>
<Dbcc ID="1" Error="8966" Severity="16" State="2">Unable to read and latch page (1:260400) with latch type SH. 23
(Data error (cyclic redundancy check).) failed. </Dbcc>
<Dbcc ID="2" Error="8954" Severity="10" State="1">CHECKDB found 0 allocation errors and 2 consistency errors not
associated with any single object.</Dbcc>
<Dbcc ID="3" Error="2533" Severity="16" State="1">Table error: page (1:258137) allocated to object ID 885682303,
index ID 16, partition ID 72057594204127232, alloc unit ID 72057594215858176 (type In-row data) was not seen. The
page may be invalid or may have an incorrect alloc unit ID in its header.</Dbcc>
<Dbcc ID="4" Error="8976" Severity="16" State="1">Table error: Object ID 885682303, index ID 16, partition ID 720
57594204127232, alloc unit ID 72057594215858176 (type In-row data). Page (1:258137) was not seen in the scan alth
ough its parent (1:257976) and previous (1:258136) refer to it. Check any previous errors.</Dbcc>
<Dbcc ID="5" Error="8978" Severity="16" State="1">Table error: Object ID 885682303, index ID 16, partition ID 720
57594204127232, alloc unit ID 72057594215858176 (type In-row data). Page (1:258138) is missing a reference from p
revious page (1:258137). Possible chain linkage problem.</Dbcc>
<Dbcc ID="6" Error="8990" Severity="10" State="1">CHECKDB found 0 allocation errors and 3 consistency errors in t
able 'ActivityPointerBase' (object ID 885682303).</Dbcc>
<Dbcc ID="7" Error="2533" Severity="16" State="1">Table error: page (1:260400) allocated to object ID 1339971950,
index ID 1, partition ID 72057594205503488, alloc unit ID 72057594217365504 (type In-row data) was not seen. The
page may be invalid or may have an incorrect alloc unit ID in its header.</Dbcc>
<Dbcc ID="8" Error="8976" Severity="16" State="1">Table error: Object ID 1339971950, index ID 1, partition ID 720
57594205503488, alloc unit ID 72057594217365504 (type In-row data). Page (1:260400) was not seen in the scan alth
ough its parent (1:14431) and previous (1:260391) refer to it. Check any previous errors.</Dbcc>
<Dbcc ID="9" Error="8978" Severity="16" State="1">Table error: Object ID 1339971950, index ID 1, partition ID 720
57594205503488, alloc unit ID 72057594217365504 (type In-row data). Page (1:260401) is missing a reference from p
revious page (1:260400). Possible chain linkage problem.</Dbcc>
<Dbcc ID="10" Error="8990" Severity="10" State="1">CHECKDB found 0 allocation errors and 3 consistency errors in
table 'AsyncOperationBase' (object ID 1339971950).</Dbcc>
<Dbcc ID="11" Error="8989" Severity="10" State="1">CHECKDB found 0 allocation errors and 8 consistency errors in
database 'Mindsharp_MSCRM'.</Dbcc>
<Dbcc ID="12" Error="8957" Severity="-1" State="1">DBCC CHECKDB (Mindsharp_MSCRM) WITH no_infomsgs executed by MI
NDSHARP\Administrator found 8 errors and repaired 0 errors. Elapsed time: 0 hours 7 minutes 16 seconds.</Dbcc>
<Dbcc ID="13" Error="8958" Severity="10" State="1">repair_allow_data_loss is the minimum repair level for the err
ors found by DBCC CHECKDB (Mindsharp_MSCRM).</Dbcc>
</DbccResults>
**Dump thread - spid = 62, PSS = 0x52C0D320, EC = 0x52C0D328
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL\LOG\SQLDump0002.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 06/20/08 14:38:58 spid 62
*
* DBCC database corruption
*
* Input Buffer 82 bytes -
* DBCC CHECKDB WITH NO_INFOMSGS
*
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump

PSS @0x52C0D320
---------------



CSession @0x52C0C278
--------------------
m_spid = 62 m_cRef = 14 m_rgcRefType[0] = 1
m_rgcRefType[1] = 1 m_rgcRefType[2] = 11 m_rgcRefType[3] = 1
m_rgcRefType[4] = 0 m_rgcRefType[5] = 0 m_pmo = 0x52C0C040
m_pstackBhfPool = 0x00000000 m_dwLoginFlags = 0x83e0 m_fBackground = 0
m_fClientRequestConnReset = 0 m_fUserProc = -1 m_fConnReset = 0
m_fIsConnReset = 0 m_fInLogin = 0 m_fAuditLoginSent = 1
m_fAuditLoginFailedSent = 0 m_fReplRelease = 0 m_fKill = 0
m_ulLoginStamp = 540428 m_eclClient = 5 m_protType = 6
m_hHttpToken = FFFFFFFF

m_pV7LoginRec
---------------------
00000000: 3c010000 03000a73 00100000 00000006 840c0000 †<......s............

00000014: 00000000 e0830000 00000000 00000000 5e000500 †................^...

00000028: 00000000 00000000 68002e00 c4000500 ce000000 †........h...........

0000003C: ce001c00 06010000 06010000 0007e959 912e0601 †...............Y....

00000050: 36003c01 00003c01 00000000 0000†††††††††††††††6.<...<.......



CPhysicalConnection @0x52C0C188
-------------------------------
m_pPhyConn->m_pmo = 0x52C0C040 m_pPhyConn->m_pNetConn = 0x52C0C7B0 m_pPhyConn->m_pConnList = 0x52C0C260
m_pPhyConn->m_pSess = 0x52C0C278 m_pPhyConn->m_fTracked = -1 m_pPhyConn->m_cbPacketsize = 4096
m_pPhyConn->m_fMars = 0 m_pPhyConn->m_fKill = 0

CBatch @0x52C0CAB8
------------------
m_pSess = 0x52C0C278 m_pConn = 0x52C0CA18 m_cRef = 3
m_rgcRefType[0] = 1 m_rgcRefType[1] = 1 m_rgcRefType[2] = 1
m_rgcRefType[3] = 0 m_rgcRefType[4] = 0 m_pTask = 0x0085B4C8


EXCEPT (null) @0x3447B748
-------------------------
exc_number = 0 exc_severity = 0 exc_func = 0x02416380



Task @0x0085B4C8
----------------
CPU Ticks used (ms) = 118929 Task State = 2
WAITINFO_INTERNAL: WaitResource = 0x00000000 WAITINFO_INTERNAL: WaitType = 0x0
WAITINFO_INTERNAL: WaitSpinlock = 0x00000000 SchedulerId = 0x0
ThreadId = 0x141c m_state = 0 m_eAbortSev = 0



EC @0x52C0D328
--------------
spid = 62 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x0 ec_atomic = 0x0 __fSubProc = 1
ec_dbccContext = 0x3447F560 __pSETLS = 0x52C0CA58 __pSEParams = 0x52C0CCF8
__pDbLocks = 0x52C0D618

SEInternalTLS @0x52C0CA58
-------------------------
m_flags = 0 m_TLSstatus = 3 m_owningTask = 0x0085B4C8
m_activeHeapDatasetList = 0x52C0CA58 m_activeIndexDatasetList = 0x52C0CA60


SEParams @0x52C0CCF8
--------------------
m_lockTimeout = -1 m_isoLevel = 4096 m_logDontReplicate = 0
m_neverReplicate = 0 m_XactWorkspace = 0x276C06B8 m_pSessionLocks = 0x52C0D828
m_pDbLocks = 0x52C0D618 m_execStats = 0x525CA508 m_pAllocFileLimit = 0x00000000




Thank you,

Tim

paulrandal
Yak with Vast SQL Skills

899 Posts
Posted - 2008-06-23 : 00:44:05
Without a backup, your only real option is to run repair. You're going to lose some data though as one of the corrupt pages is ina clustered index. You can tell which key values you're going to lose using the technique I blogged about a couple of weeks ago:
[url]http://www.sqlskills.com/blogs/paul/2008/06/09/CHECKDBFromEveryAngleUsingDBCCPAGEToFindWhatRepairWillDelete.aspx[/url]

And get a decent backup strategy so that the next time it happens you won't lose data. You also need to figure out why it happened in the first place - looks like IO subsystem-caused corruption to me.

Thanks

Paul Randal
SQL Server MVP, Managing Director, SQLskills.com
Go to Top of Page

tunterberger
Starting Member

2 Posts
Posted - 2008-06-23 : 11:35:36
Thank you for the information Paul. I figured there would be data loss. This is an issue I have somewhat inherited after the fact, and a backup strategy will definitely be in place once we get this resolved.

Tim
Go to Top of Page
   

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources

Articles

Forums

Blogs

Contact Us

About the Site