|
Home > Archive > MS SQL Server > February 2006 > ums schedule hang issue.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
ums schedule hang issue.
|
|
| soonyu 2006-02-13, 7:23 am |
| have ums schedule hang issue.
information as below. any specific microsoft document / solution / case same
as this?
sql dump minidump and start put message sql error log
1 Error: 3624, Severity: 20, State: 1.
2. Error: 17883, Severity: 1, State: 0
3. The Scheduler 3 appears to be hung. SPID 0, ECID 0, UMS Context 0x03AA3B50.
4. Error: 17883, Severity: 1, State: 0
5. The Scheduler 3 appears to be hung. SPID 0, ECID 0, UMS Context 0x03AA3B50.
6. Error: 17883, Severity: 1, State: 0
7. The Scheduler 3 appears to be hung. SPID 0, ECID 0, UMS Context 0x03AA3B50.
8. 3 Time out occurred while waiting for buffer latch type 2,bp 0x13cfd40,
page
3:4935808), stat 0x40d, object ID 8:2012586258:0, EC 0x65944098 : 14,
waittime 300. Not continuing to wait.
9. Waiting for type 0x2, current count 0x10002a, current owning EC 0x65A6C098.
10. WARNING: EC 67950098, 13 waited 300 sec. on latch 19d6b454. Not a BUF
latch.
11 WARNING: EC 62f04098, 11 waited 300 sec. on latch 19d6b454. Not a BUF
latch.
12. WARNING: EC 6342e098, 10 waited 300 sec. on latch 19d6b454. Not a BUF
latch.
13. Waiting for type 0x4, current count 0xa, current owning EC 0x40FA0098.
and the above information keep repeat
event log
------------
Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 91, PSS = 0x58995240, EC = 0x58995568
*Stack Dump being sent to e:\SQLdata\MSSQL\log
\SQLDump0002.txt
* ********************
********************
********************
*
Stack Signature for the dump is 0xF63BD390
part of minidump
--------------------
* Short Stack Dump
* 0087A90E Module(sqlservr+0047
A90E)
(CStackDump::GetCont
extAndDump+0000002E)
* 0087C41F Module(sqlservr+0047
C41F) (stackTrace+00000223
)
* 00931097 Module(sqlservr+0053
1097) (utassert_fail+00000
2E3)
* 00617F6C Module(sqlservr+0021
7F6C) (CMsqlXact::SetNewWs
id+000000B7)
* 00617B66 Module(sqlservr+0021
7B66) (CMsqlXact::EnlistDT
CXact+000001BF)
* 008625E3 Module(sqlservr+0046
25E3) (rm_ods_handler_body
+00000D36)
* 008616C8 Module(sqlservr+0046
16C8) (rm_ods_handler+0000
0053)
* 006719DF Module(sqlservr+0027
19DF) (process_commands+00
0001F8)
* 41075002 Module(UMS+00005002)
(ProcessWorkRequests
+00000272)
* 41074698 Module(UMS+00004698)
(ThreadStartRoutine+
00000098)
* 77BC90A2 Module(MSVCRT+000290
A2) (endthread+000000A6)
* 77E4A990 Module(kernel32+0000
A990) (FlsSetValue+0000077
9)
| |
| John Bell 2006-02-13, 7:23 am |
| Hi
You may want to check http://support.microsoft.com/kb/909734 regarding
missing information.
John
"soonyu" wrote:
> have ums schedule hang issue.
> information as below. any specific microsoft document / solution / case same
> as this?
>
> sql dump minidump and start put message sql error log
> 1 Error: 3624, Severity: 20, State: 1.
> 2. Error: 17883, Severity: 1, State: 0
> 3. The Scheduler 3 appears to be hung. SPID 0, ECID 0, UMS Context 0x03AA3B50.
> 4. Error: 17883, Severity: 1, State: 0
> 5. The Scheduler 3 appears to be hung. SPID 0, ECID 0, UMS Context 0x03AA3B50.
> 6. Error: 17883, Severity: 1, State: 0
> 7. The Scheduler 3 appears to be hung. SPID 0, ECID 0, UMS Context 0x03AA3B50.
> 8. 3 Time out occurred while waiting for buffer latch type 2,bp 0x13cfd40,
> page
> 3:4935808), stat 0x40d, object ID 8:2012586258:0, EC 0x65944098 : 14,
> waittime 300. Not continuing to wait.
> 9. Waiting for type 0x2, current count 0x10002a, current owning EC 0x65A6C098.
> 10. WARNING: EC 67950098, 13 waited 300 sec. on latch 19d6b454. Not a BUF
> latch.
> 11 WARNING: EC 62f04098, 11 waited 300 sec. on latch 19d6b454. Not a BUF
> latch.
> 12. WARNING: EC 6342e098, 10 waited 300 sec. on latch 19d6b454. Not a BUF
> latch.
> 13. Waiting for type 0x4, current count 0xa, current owning EC 0x40FA0098.
>
> and the above information keep repeat
>
> event log
> ------------
> Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 91, PSS = 0x58995240, EC = 0x58995568
> *Stack Dump being sent to e:\SQLdata\MSSQL\log
\SQLDump0002.txt
> * ********************
********************
********************
*
> Stack Signature for the dump is 0xF63BD390
>
> part of minidump
> --------------------
> * Short Stack Dump
>
> * 0087A90E Module(sqlservr+0047
A90E)
> (CStackDump::GetCont
extAndDump+0000002E)
> * 0087C41F Module(sqlservr+0047
C41F) (stackTrace+00000223
)
>
> * 00931097 Module(sqlservr+0053
1097) (utassert_fail+00000
2E3)
>
> * 00617F6C Module(sqlservr+0021
7F6C) (CMsqlXact::SetNewWs
id+000000B7)
>
> * 00617B66 Module(sqlservr+0021
7B66) (CMsqlXact::EnlistDT
CXact+000001BF)
>
> * 008625E3 Module(sqlservr+0046
25E3) (rm_ods_handler_body
+00000D36)
>
> * 008616C8 Module(sqlservr+0046
16C8) (rm_ods_handler+0000
0053)
>
> * 006719DF Module(sqlservr+0027
19DF) (process_commands+00
0001F8)
>
> * 41075002 Module(UMS+00005002)
(ProcessWorkRequests
+00000272)
>
> * 41074698 Module(UMS+00004698)
(ThreadStartRoutine+
00000098)
>
> * 77BC90A2 Module(MSVCRT+000290
A2) (endthread+000000A6)
>
> * 77E4A990 Module(kernel32+0000
A990) (FlsSetValue+0000077
9)
|
|
|
|
|