Archives of the TeradataForum

Message Posted: Fri, 07 Jul 2006 @ 20:07:02 GMT

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

Glen made this point:

----------------

In V2R6.1 this limit has apparently been raised to 30 loads and 60 unloads (i.e. fastexport).

Either way, the limit is set in the "dbscontrol" record - MaxLoadTasks.

----------------

A second part of that utility limit enhancement in 6.1 is a new DBScontrol setting called MaxLoadAWT. In fact, if you don't have MaxLoadAWT set to non-zero (zero is the default), you will not be able to take advantage of the higher concurrent load utility limit.

MaxLoadAWT limits how many AMP worker tasks can be used by fastloads and multiloads at any point in time, based on their AMP worker task demand. The max allowable MaxLoadAWT setting is 60% of the total AWTs. A new fastload or multiload job is only allowed to start if both MaxLoadTasks and MaxLoadAWT limits have not been reached.

The point of this is to allow more load jobs, if desired, but not if they would consume what is for you an unreasonable number of AMP worker tasks. There is sensitivity in the product to which phase of loading a job is in, and how many AWTs are being used. When one fastload moves into Phase 2, when fewer AWTs are used, then a new multiload job might be able to be started up, as an example.

Thanks, -Carrie

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