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


Add to briefcase

Database gone into Suspect mode after the execution of an SP Expand / Collapse
Author
Message
Posted Wednesday, April 10, 2013 1:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, October 29, 2014 1:45 PM
Points: 1, Visits: 30
SQL Server Version: 2005 Standard RTM version 9.00.1406.00

A Stored Procedure(This SP Runs everyday but has never caused suspect mode) was running which does a large amount of data transfer within a transaction. The transaction might remain active for about 15 to 20 minutes. There might also be other processes accessing the table which is under transaction. So blocking might have been occurring. The Database went into suspect Mode generating huge number of Dump files. The DB was however restored from the Backup files. My concern is that the same issue could rise again as we are not able to identify the problem behind it.

Some error data from Dump files:

First File Dump File:

* 04/04/13 01:18:16 spid 95
* Location: lckmgr.cpp:9421
* Expression: NULL == m_lockList.Head ()

Second Dump File:

* 04/04/13 01:18:20 spid 95
* Exception Address = 0000000000000000 Module(sqlservr+FFFFFFFFFF000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 0000000000000000

Third Dump File:

* 04/04/13 01:18:23 spid 95
* Location: "xact.cpp":2630
* Expression: !m_updNestedXactCnt
* SPID: 95
* Process ID: 268
* Description: Trying to use the transaction while there are 1 parallel nested xacts outstanding

Fourth Dump File:

* 04/04/13 01:18:43 spid 95
* ex_raise2: Exception raised, major=52, minor=42, state=1, severity=22

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Begin transaction log dump for database 'DB_Name'; for rollback failure - filter XdesId.

--Huge Number of Transaction Log Entries Here--

Fifth Dump File:

* 04/04/13 01:21:40 spid 18
* Location: page.cpp:4245
* Expression: spaceNeeded <= spaceContig && spaceNeeded <= space_usable

Sixth Dump File:

* 04/04/13 01:21:40 spid 18
* HandleAndNoteToErrorlog: Exception raised, major=34, minor=48, severity=21


Next Dump File:


* 04/04/13 01:21:57 spid 21
* Location: page.cpp:4100
* Expression: !pageFull
* SPID: 21

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Begin transaction log dump for database 'DB_Name'; for REDO failure - filter on PageId.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Begin transaction log dump for database 'DB_Name'; for REDO failure - filter XdesId.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Begin transaction log dump for database 'DB_Name'; for recovery failure - no filter.

Seventh Dump File:

* 04/04/13 01:24:39 spid 98
* Exception Address = 000000000288FC14 Module(sqlservr+000000000188FC14)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 0000000000000000

Eighth Dump File:

* 04/04/13 01:24:41 spid 98
* Location: T:\Yukon\sqltdbms\storeng\dfs\manager\lckmgrp.h:675
* Expression: m_iteratorInSafeState

Nineth Dump File:

* 04/04/13 01:24:41 spid 98
* ex_terminator - Last chance exception handling
Post #1440687
Posted Wednesday, April 10, 2013 2:21 AM


SSC-Forever

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

Group: General Forum Members
Last Login: 2 days ago @ 1:14 PM
Points: 40,615, Visits: 37,081
The very first thing I will suggest is patch that instance. You're running RTM of SQL 2005 which had some nasty problems in it. Patch up to SP4 ASAP.



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

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

Post #1440697
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse