Archives of the TeradataForum

Message Posted: Tue, 01 Nov 2005 @ 10:05:47 GMT

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

Srikanth,

The usual order of creating priority scheduler components is:

1. resource partition

2. allocation group

3. performance group

You need to create the allocation groups and the resource partitions prior to creating the performance groups because the performance group definition references those other objects. So they must pre-exist the performance group definition command.

One difficulty you may be having is if you are trying, as you say, to associate a resource partition with an allocation group. It can't be done. When you create an allocation group it just sits out there like an unfertilized egg, with no actual context or purpose.

Only when you define the performance group in which you reference that allocation group will the allocation group take on a specific association and purpose. And that association will include a specific resource partition--whichever resource partition is referenced in that performance group definition.

Once an allocation group has been associated to a performance group and that performance group's resource partition, from that point on it can only be associated to other performance groups within the same resource partition.

It might be helpful for you to read the Orange Book on Priority Scheduler, which is avaiable through the following path:

-- Go to NCR@YourService

-- At bottom of page under Services select "NCR@YourService"

-- You are then prompted to enter your used ID and password to get into the site

-- Once you're on the site, under Teradata Applications select "My Support Link"

-- In the left hand column select "Teradata Documentation and Resources"

-- In the left hand column select "Teradata Orange Books"

Good luck, -Carrie

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