Archives of the TeradataForum

Message Posted: Wed, 06 Dec 2006 @ 17:15:09 GMT

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

<-- Anonymously Posted: Wednesday, December 06, 2006 09:15 -->

You can't see spool usage during use so peakspool will supposedly give you that information after the fact.

If you ran macro to clean peak then you just lost that information. The spool is temporary usage so it should automatically clear after the use or the failure. (There were some left over spool issue reported since V2R5 so that is exception).

You can use the following query to see where the problem may be after you encounter your out of spool condition before your clear the peak value: Keep in mind the allocated spool is equally allocated to the logical process unit (AMPs).

     sel databasename, sum(peakspool), max(peakspool)*(hashamp()+1),
     max(peakspool), avg(peakspool), min(peakspool)
     from dbc.diskspace
     where databasename=
     group by 1
     ;

Hope this helps.

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