Archives of the TeradataForum
Message Posted: Mon, 09 Nov 2015 @ 12:47:35 GMT
Spool space has a maximum per amp. Therefore, you can run out before you reach the total spool allocated.
Also spool can be allocated at the user level or the profile. The profile spool takes precedence over the user spool.
Therefore I am guessing you have one of two situations. You are running out of spool on one amp due to skew.
Or you Think the user has more spool than really allocated. This will happen when you look at the user spool instead of the profile spool.
This query should show you the proper results. This assumes that no other queries that use more spool have been run since the last time that peakspool was reset for the user.
SELECT a.databasename (CHAR(10)) ,a.vproc ,sum(a.currentspool) (format'zzz,zzz,zzz,zzz') (char(15)) as current_spool ,sum(a.peakspool) (format'zzz,zzz,zzz,zzz') (char(15) ) as Peak_spool ,sum(coalesce(a.MaxProfileSpool ,a.maxspool) ) (format'zzz,zzz,zzz,zzz') (char(15)) as max_spool from dbc.diskspacev a where a.databasename = 'xxxx' -- replase xxxx with the username group by 1,2 order by 3 desc,2 ;
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|