Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 10 Mar 2006 @ 16:47:47 GMT


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


Subj:   Re: MLoad session calculations
 
From:   Diehl, Robert

Until you start to run TASM in V2R6.1, there is a limit on the number of concurrent fastload, multiload and fastesports. Default is 5 max is 15. This can be found in DBS control MAXLOADTASKS I think it is General number 11. NO matter what limit is set you want to add Tenacity to your fastload and mutliload jobs.

Tenacity 2


Will keep trying every 6 minutes for 2 hours.

I would also evaluate whether 20 sessions is appropriate for the volume loaded. Only real way to now is try it with several different session counts. Best way is to make number of sessions dynamic variable so you can change as needs dictate. You can also set a default by creating a mloadcfg.dat file. See Mload book for specifics.

On another note. If you allow 5 concurrent loads, it will consume 200 sessions. You can only logon 120 sessions per Parsing Engine (PE). Just be aware so you don't consume all the available sessions when raising this limit. Each node generally has 1 or two PE's. Easy way to see number of PE's is to look at PMON top center. Also sessions are not tied to the PE's on the node/ip you logon. Teradata balances the sessions across all the PE's for you.


Thanks,

Bob Diehl
Travelocity.com



     
  <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: 15 Jun 2023