FIX: Stack Overflow If a SELECT Statement Is KilledID: Q159339
|
If a process is killed while running a SELECT statement in which an
aggregate function is used with a DISTINCT keyword, the following error
message is displayed in the errorlog:
spid10 ex_testhandle: stack overflow, top=0x10a0ac8, end=0x10a0ac8
kernel udread: Operating system error 6(The handle is invalid.) on
device 'D:\MSSQL\DATA\MASTER.DAT' (virtpage 0x00000394).
kernel udwritem: Operating system error 6(The handle is invalid.) on
device 'D:\MSSQL\DATA\MASTER.DAT' (virtpage 0x00000b80).
spid10 bufwait: timeout, BUF_IO, bp 0xca1420, pg 0x110, stat
0x1004/0x6, obj 0, bpss 0x109f598
Error: 1117, Severity: 21, State: 10
Extent chain for object -321 is not correctly linked.
Avoid using the Kill command to terminate processes.
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.
The following SELECT statement is an example of a statement that will cause
this problem to occur:
select avg (distinct Number) from Table
Additional query words: freeze frozen hung lock err msg errmsg
Keywords : kbinterop kbnetwork kbusage SSrvErr_Log kbbug6.50 kbfix6.50.sp2
Version : 6.5
Platform : WINDOWS
Issue type :
Last Reviewed: April 4, 1999