maxagents - Maximum number of agents configuration parameter
This parameter has been deprecated since Version 9.5, but is still being used by pre-Version 9.5 data servers and clients. Any value specified for this configuration parameter will be ignored by the database manager in Db2® Version 9.5 or later releases.
- Configuration type
- Database manager
- Applies to
-
- Database server with local and remote clients
- Database server with local clients
- Partitioned database server with local and remote clients
- Parameter type
- Configurable
- Default [range]
- 200 [1 - 64 000]
400 [1 - 64 000] on partitioned database server with local and remote clients
- Unit of measure
- Counter
If you want to limit the number of coordinating agents, use the max_coordagents parameter.
This parameter can be useful in memory constrained environments to limit the total memory usage of the database manager, because each additional agent requires additional memory.
Recommendation: The value of maxagents should be at least the sum of the values for maxappls in each database allowed to be accessed concurrently. If the number of databases is greater than the numdb parameter, then the safest course is to use the product of numdb with the largest value for maxappls.
Each additional agent requires some additional processing resources that are allocated at the time the database manager is started.
- In a non-partitioned database environment with no intra-query parallelism enabled, increase the value of the maxagents database configuration parameter.
- In a partitioned database environment or an environment where intra-query parallelism is enabled, increase the larger of maxagents or max_coordagents.