Archives of the TeradataForum

Message Posted: Fri, 07 Mar 2003 @ 13:12:26 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

We've experienced the problem occasionally. NCR and I have never been able to trace how it's happening. It has to be the user cancelling a query in some new and unusual way.

I had closed the incident since our last patch upgrade but I see it's back so I'll re-open the incident.

In the short term, you can clear the phantom spool using the following method:

Determine who has spool but isn't signed on:

SELECT DATABASENAME, VPROC, CURRENTSPOOL
FROM DBC.DISKSPACE
WHERE DATABASENAME NOT IN (SEL USERNAME FROM DBC.SESSIONINFO)
AND DATABASENAME <> 'DBC'
AND CURRENTSPOOL > 0
ORDER BY 1,2;

Through the supervisor window,

start updatespace

from whatever window it's started in

update spool for xxxx;

That should clear the account record. Disk space is not being used for the user, they're just not able to get as much spool as they should because the accounting indicates that they're holding some.

Ruth Fenwick
IA&DSS Team Leader, IRM
Hudson's Bay Company

	<Prev	Next>		<<First	<Prev	Next>	Last>>