maxspool value wrong in dbc.diskspaceV?

Database
Enthusiast

maxspool value wrong in dbc.diskspaceV?

Hi experts,

when submitting the query

SELECT
databasename,
SUM(maxperm),
SUM(Maxtemp),
SUM(maxspool),
SUM(peakspool)
FROM
dbc.diskspaceV
WHERE databasename = 'XXX'
GROUP BY databasename

I get the following result

DatabaseName Sum(MaxPerm) Sum(MaxTemp) Sum(MaxSpool) Sum(PeakSpool)

XXX 0,00 0,00 0,00 626688,00

As XXX is our user created for running ETL jobs I don't expect the 0 values for Sum(MaxTemp) and Sum(MaxSpool). I know for a fact that when logged in with this user I can insert data in global temp tables so this user should have temp space allocated, right? Also how can I have a Sum(PeakSpool) > 0 while my Sum(MaxSpool) = 0?

If I check the database information with teradata administrator for this user I have also 0 values for Spoolspace and Tempspace, however when I go to the direct owner of this user and check the child space I get (for my child XXX in question) values that make more sense:

Name CurrentPerm MaxPerm PeakPerm MaxSpool PeakSpool MaxTemp PeakTemp

...

XXX 0 0 0 4.500.000.000.000 626.688 4.500.000.000.000 0

...

Anyone out there who can explain this because I am very confused ....

Thanks,

Sven

Tags (1)
2 REPLIES
Junior Contributor

Re: maxspool value wrong in dbc.diskspaceV?

Hi Sven,

the spool of this user is assigned via a PROFILE, there are two columns for Spool/Temp: 

SELECT
databasename,
SUM(maxperm),
SUM(COALESCE(MaxProfileTemp,Maxtemp)),
SUM(COALESCE(MaxProfileSpool,maxspool)),
SUM(peakspool)
FROM
dbc.diskspaceV
WHERE databasename = 'XXX'
GROUP BY databasename
Enthusiast

Re: maxspool value wrong in dbc.diskspaceV?

Hi,

I am not surprised the answer should come from THE expert.

Thanks for clarifying that Dieter.

Sven