DB2 - Problem description
Problem IC96960 | Status: Closed |
INTERRUPT POOLED DATABASE AGENTS WHICH ARE SERVING NEW APPLICATIONS THAT HAVE NOT CONNECTED TO THE DATABASE YET. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
During graceful takeover, the existing logic on primary will force all applications and kick off all pooled agents to dissociate from the database. If a pooled database agent is picked to serve a new application that is not fully connected to the database, this pooled agent will not be interrupted and so the primary will end up waiting for the pooled agent to terminate processing on its own. We are adding new interrupt support to interrupt these kind of agents as well. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * During graceful takeover, the existing logic on primary will * * force all applications and kick off all pooled agents to * * dissociate from the database. * * If the pooled database agent is picked to serve new * * application * * that are not fully connected to the database, this pooled * * agent * * will not be interrupted. We are adding new interrupt * * support * * to interrupt this kind of agents as well. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to v10fp3 * **************************************************************** | |
Local Fix: | |
To prevent this issue, update num_poolagents DBM configuration parameter to 0 for HADR database to ensure no pooled database agents exist. Please consult the information center on num_poolagents, since modifying this parameter can have performance consequences. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC97376 IT05792 IT05795 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.10.2013 27.11.2014 27.11.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |