|
Problem IC97376
|
Status: Closed |
INTERRUPT POOLED DATABASE AGENTS WHICH ARE SERVING NEW APPLICATIONS THAT HAVE NOT CONNECTED TO THE DATABASE YET. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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: |
|
| Local Fix: |
Update num_poolagents DBM configuration parameter to 0 for HADR
database. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Comment |
This APAR is a duplicate of IC96960 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.11.2013
07.03.2014
27.11.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
