resource-locking issues [may be caused by Idle Agents ]

[gbag]

Hi,
I am having problems with resource-locking issues. We had the CPU-bound and Memory-Bound situation. When we looked at the processes, there were lot of db2agent (idle) processes.
This we saw even when all the applications were disconnected. Are these processes the cause for the resource consumption.If yes, how to get rid of them.
To the wonder, there was no error message in the db2diag.log file. And we are not using the connection concentrator.
Any help is highly appreciated.
Thanks

 

[sathyarams]

db2 get dbm cfg

will show the value for num_poolagetnts and num_initagents

The NUM_INITAGENTS parameter determines the initial number of idle agents that are created in the agent pool at DB2START time.

The NUM_POOLAGENTS parameter is a guideline for how large you want the agent pool to grow. If more agents are created than is indicated by the value of this parameter, they will be terminated when they finish executing their current request, rather than be returned to the pool. If the value for this parameter is 0, agents will be created as needed, and may be terminated when they finish executing their current request.

HTH

Sathyaram

For db2 resoruces visit

http://www.db2click.com

More DB2 questions answered at

http://www.dbforums.com/f8

&

http://www.idug.org/user/UserLogin.asp

 

[gbag]

Thanks Sathyaram,
Is more no. of agents bad for DB2 or for the system?
thanks

 

[sathyarams]

If your system is has resource constraints (memory and CPU), then having more agents will hurt the system and in turn db2

HTH

Sathyaram

For db2 resoruces visit

http://www.db2click.com

More DB2 questions answered at

http://www.dbforums.com/f8

&

http://www.idug.org/user/UserLogin.asp