Archives of the TeradataForum
Message Posted: Tue, 01 Jul 2003 @ 21:52:28 GMT
Often? That's depressing. It sometimes takes a few minutes to release all spool, so I'd wait a while and check again. If the spool doesn't go away, it's possible you have "leftover spool." That is, spool that was not properly released when it should have been. Here's the query that is often used to search for leftover spool:
sel databasename ,sum(currentspool) from DBC.DiskSpace where databasename NOT IN (sel username from DBC.SessionInfo) group by 1 having sum(currentspool) > 0 order by 2 desc;
This looks for users not logged on that have currentspool greater than zero.
Practically speaking, there's no way to get rid of leftover spool other than restarting the system. It's theoretically possible to use filer to do the job, but it would have to be done file by file making it too tedious to be practical.
And even if the query above returns some rows, it's possible you have "bogus" spool rather than "leftover" spool. What's the difference? Leftover spool actually exists. Bogus spool doesn't. It just looks like it does because the data in DBC.DatabaseSpace has been corrupted.
If the query above returns rows, you have one of these problems and should probably open an incident with NCR.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|