SQL Assertion error
-
Hi,
I am getting this stack dump everyday with the following error. This is a production server. Server is SQL 7.0 with SP4 and hotfix Q316333
SQL Server Assertion: File: <somerge.c>, line=2808
Failed Assertion = 'sortdesP->soTimerActive'.
*******************************************************************************
*
* BEGIN STACK DUMP:
* 06/01/05 09:58:36 spid 188
*
* Input Buffer 135 bytes -
* $ s p s u n _ r p _ P R D 0 0 7 _ X X _ v 4 _ P r d S u m r y R e s c ;
* 1 % % 20020101 20251231 # 310755
*
*******************************************************************************
-------------------------------------------------------------------------------
Short Stack Dump
0x77f67a6b Module(ntdll+7a6b) (ZwGetContextThread+b)
0x0078d260 Module(sqlservr+38d260) (utassert_fail+1a0)
0x006e91b8 Module(sqlservr+2e91b8) (mergeread+151)
0x006e8042 Module(sqlservr+2e8042) (mergeprepare+110)
0x006e7d5c Module(sqlservr+2e7d5c) (mergeruns+c7)
0x006e7b08 Module(sqlservr+2e7b08) (bestmerge+130)
0x005aed9a Module(sqlservr+1aed9a) (sort_addpage+2ef)
0x005aeb29 Module(sqlservr+1aeb29) (soAllocRecBuf+83)
0x00517b94 Module(sqlservr+117b94) (RowsetSorted::InsertRow+77)
0x00517b2f Module(sqlservr+117b2f) (RowsetChangeSort::InsertRow+1b)
0x0041c7e6 Module(sqlservr+1c7e6) (CValRow::SetDataX+24)
0x0040ff69 Module(sqlservr+ff69) (SetMultData+1c)
0x0040fd11 Module(sqlservr+fd11) (CEs::GeneralEval+c7)
0x00517aeb Module(sqlservr+117aeb) (CQScanSort:
ushRow+20) 0x005179e4 Module(sqlservr+1179e4) (CQScanSort::FillSortTable+ac)
0x00517842 Module(sqlservr+117842) (CQScanSort:
pen+63) 0x0041f93c Module(sqlservr+1f93c) (CQScan:
pen+1c) 0x00421ec0 Module(sqlservr+21ec0) (CQScanTop:
pen+e) 0x0041f93c Module(sqlservr+1f93c) (CQScan:
pen+1c) 0x0050d690 Module(sqlservr+10d690) (CQScanUpdate:
pen+16) 0x00416133 Module(sqlservr+16133) (CQueryScan::Startup+a3)
0x00413db3 Module(sqlservr+13db3) (CStmtQuery::FExecuteQuery+258)
0x0041c658 Module(sqlservr+1c658) (CStmtDML::XretExecuteNormal+1c7)
0x00610bd7 Module(sqlservr+210bd7) (CStmtSelectInto::XretExecute+14a)
0x00413171 Module(sqlservr+13171) (CMsqlExecContext::ExecuteStmts+11b)
0x00412cf4 Module(sqlservr+12cf4) (CMsqlExecContext::Execute+1bb)
PSS @0x8A8E7118
---------------
pspid = 188 m_dwLoginFlags = 0x03e0 plsid = 449
pbackground = 0
pbSid
-----
1725fffffff7dff11 ff4f0050 ff6036ff a
sSecFlags = 0x2
pdeadlockpri = 0 poffsets = 0x0 pss_stats = 0x0
ptickcount = 572343359 pcputickcount = 314772215166826
ploginstamp = 129243 ptimestamp = 2005-06-01 09:45:36.660
prowcount = 54448 plangid = 0 pdateformat = 1
pdatefirst = 7 Language = us_english RemServer =
UserName = CRYSTAL HostName = poptions = 0x20000020
poptions2 = 0x1d020 pline = 149 pcurstepno = 5
prowcount = 54448 pstatlist = 0 pcurcmd = 194
pseqstat = 0 ptextsize = 2147483647 pretstat = 0
pslastbatchstarttime = 1900-01-01 00:00:00.000 pmemusage = -3151
hLicense = -1 tpFlags = 0x1 isolation_level = 1
fips_flag = 0x0 sSaveSecFlags = 0x0 psavedb = 0
pfetchstat = 0 pcrsrows = 0
pslastbatchtime = 2005-06-01 09:45:36.690 pubexecdb = 0
fInReplicatedProcExec = 0 pdelimitor = pxcb = 0x9db86028
pxcb->xcb_xactcnt = 1 pxcb_lock_recursion = 0 pdlckseq = 0
presSemCount = [569]2324591304
presSemCount = [0]2324591304 pcputot = 0
pcputotstart = 0 pcpucmdstart = 0 pbufread = 64895
pbufreadstart = 0 plogbufread = 3970402 plogbufreadstart = 1119
pbufwrite = 17 pbufwritestart = 0 pLockTimeout = 4294967295
pec
---
ecid = 0 ec_stat = 0x400 pcurdb = 7
ec_curckptdb = 0x0 ec_lasterror = 0 ec_preverror = 0
ec_cpucur = 3882750 ec_cmderrs = 0 ec_timeslice = 100
ec_dbtable = 0x800b0880 ec_reswait = 0x0 ec_dbindex = -1
psrvproc->eclClient = 2 psrvproc->status = 32 psrvproc->bNewPacket = 0
psrvproc->pmo = 0x8e10a028
psrvproc->ums_context = 0xde2f70
psrvproc->pV7LoginRec
---------------------
00000000: e8000000 00000070 00100000 00000006 d9450000 .......p.........E..
00000014: 00000000 e0030000 00000000 09080000 56000000 ................V...
00000028: 56000700 64000700 72000000 72000d00 00000000 V...d...r...r.......
0000003c: 8c000400 94000000 94000d00 0008023e 39ebae00 ...............>9...
00000050: 3a00e800 00004300 :.....C.
Top SRV_RPCINFO structure
---------------------------
00000000: 01000000 00000000 00000000 00000000 00000000 ....................
00000014: 00000000 b0f4bf4c 68f4bf4c 22000000 00000000 .......Lh..L".......
00000028: 00000100 05000100 fcf4bf4c
any ideas/solutions for this would be greatly appreciated.
Thanks
-
This was removed by the editor as SPAM
-
I don't see anything there that I can specifically address, but I would call MS to open up a ticket with them. They'll charge you, but I have usually found it to be well worth the price. Plus, if it is found to be a bug, they refund your money.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
-
If you're still having a problem.... (I was out of town the month of June and am catching up)
Lots of stuff can cause dumps, still, they are normally fairly rare. Pay attention to the topmost section, the rest is diagnostics that are meaningful mainly only to MS techs.
The code
* $ s p s u n _ r p _ P R D 0 0 7 _ X X _ v 4 _ P r d S u m r y R e s c ;
Does this mean anything to you? It looks like some sort of procedure name to me.
I would also look to see if this problem is occuring at the same time daily, which could indicate a scheduled job and a further clue. If it's still happening, I would definitely follow DC's advice and pay for a ticket with MS, they can trace it down pretty quick.
We had a weird dump happen under 6.5. The server would crash and the SQL log would report some sort of a cursor exception, but none of our code used cursors! Turns out it was an ActiveX-type object in a VB program that invoked cursors internally. MS had us fixed in a day, the repair was to add a startup parameter.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font] -
I was having exactly the same problems as you, until I called Microsoft support. There is an updated build of SQL Server available, build 1145, which has fixed the issue for us.
I've wrote about it in my blog
Tom.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply