DB2 - Problem description
| Problem IC68847 | Status: Closed |
LOCAL CLIENT ABNORMAL TERMINATION STAYS UNDETECTED BY DATABASE ON WINDOWS. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
The abnormal termination of a local connection to the database ( e.g. killed via taskmanager ) will remain undetected by the database server and lead to resources not being cleaned up on the server side. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of DB2 on Windows * **************************************************************** * PROBLEM DESCRIPTION: * * An abnormal end of a local connection to the database may * * remain undetected by the database server , leading to * * resources being held at the database server. * **************************************************************** * RECOMMENDATION: * * Upgrade the database server to DB2 V9.7 Fix Pack 3 * **************************************************************** | |
| Local Fix: | |
The server side resources need to be removed manually using the "force applications" command. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
This problem was first fixed in DB2 V9.7 Fix Pack 3 | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69140 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.05.2010 24.09.2010 24.09.2010 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.3 |
|
| 9.7.0.3 |
|