Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Fri, 18 May 2001 @ 15:03:37 GMT

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

Subj:   Re: Monitoring long-running queries
From:   David Wellman


Welcome to Teradata !

Firstly, logging on with multiple sessions for this type of query won't buy you anything. A single session will still utilise all amps (assuming you don't have skewed data).

Try the following queries;

sel vprocid,currentperm
from dbc.tablesize
where databasename= 'name of database containing table B'
and tablename= 'B'
order by 2 desc;

If the value for each currentperm is 512 (or maybe 1024) then the insert portion hasn't started yet. you're still on the select portion.

If you're still on the select, then try;

sel sum(currentspool) (named 'total spool')
,100 * avg(currentspool)/max(currentspool) (named 'spool eff %')
from dbc.diskspace
where databasename= 'username of userid running the bteq job';

This will tell you how much spool that user is using and how evenly distributed it is (100%) is good.

These will tell you whether you're doing the select or doing the insert. There probably isn't much else in this type of processing.

Particularly given that you're creating a table, it may be worth checking that the user session isn't blocked in anyway. Use PMON (part of Teradata manager), or Qrysessn from the dbw to check the status of the job in question. You should be seeing a status of ACTIVE.

Try those and see where you get to.



  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016