DB2 - Problem description
Problem IC65685 | Status: Closed |
IN A DPF ENVIRONMENT, SUBAGENTS ARE NOT BEING POOLED AFTER EXECUTING CRITICAL TASKS. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In a DPF environment, subagents are assigned to handle requests for an application. After executing a request that is deemed critical such as a commit or rollback, the subagent is terminated rather than going back into the pool to handle future requests. If there are no available agents in the pool then a new agent must be started to handle the request. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Improved db2agent pooling. * **************************************************************** * PROBLEM DESCRIPTION: * * See the APAR description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 9.7 fixpack 2. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.01.2010 25.05.2010 25.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |