Archives of the TeradataForum
Message Posted: Fri, 07 Mar 2003 @ 13:12:26 GMT
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
Through the supervisor window,
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.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|