 |
 |
Archives of the TeradataForum
Message Posted: Tue, 06 Sep 2005 @ 13:58:00 GMT
Subj: | | Re: Flushing Residual Spool From Amps |
|
From: | | Victor Sokovin |
| I asked our DBA's, but they implied that only a Teradata technician can flush away residual spool from the system. This seems unlikely.
Is there a way for a standard user to flush all of their running jobs off the amps? | |
I think your DBAs might be right. If the residual spool has been hanging around for such a long time, something is probably wrong with it. We
have had a few threads on spool management (if interested, you should be able to find them in the archives), and a few problems have been reported
in this area.
Did you try to run a "wild" query which would potentially consume *all* available spool space? It might help get rid of the old spool file but
I would not bet on it.
Regards,
Victor
| |