Archives of the TeradataForum
Message Posted: Tue, 06 Sep 2005 @ 13:50:00 GMT
Subj: | | Re: Flushing Residual Spool From Amps |
|
From: | | Fenwick, Ruth |
I've seen this phantom spool from time to time and have yet to figure out the cause. It is an accounting issue where some table is not being
updated properly and Teradata thinks you're using spool you're not. It gets cleared on a database restart (which hopefully doesn't happen too
often at your shop).
Sometimes it takes a few minutes to clear, but it doesn't sound like it ever clears in your case. I know of no way for a 'user' to flush the
spool, but the following can be done by someone with UNIX root authority.
from the supervisor window
Start updatespace
from whatever window it's started in
update spool space for username;
I've attached the SQL I use to check if there is any 'phantom' spool. It only works for users not signed on. I know of no why to check
spool usage for users currently signed on (how to tell if they're really using spool or it's phantom)
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;
|