|
Problem IT17501
|
Status: Closed |
CLIENT SIDE PERFORMANCE PROBLEMS IN CASE OF MISSING DB2TRC SHARED MEMORY SEGMENT
|
| product: |
DB2 CONNECT / DB2CONNCT / A50 - DB2 |
| Problem description: |
In some cases, client side applications allocate the db2trc IPC
resources up front.
see e.g.
http://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.
ibm.swg.im.dbclient.config.doc/doc/r0059504.html
These resources typically exist of a semaphore and a shared
memory segment.
If for some external reason, the shared memory segment no longer
exists but the semaphore is still there. Then the trace
infrastructure will repeatedly perform expensive checks causing
a severe ( client side ) slowndown in the application.
This APAR increases the resilience within DB2 for such scenario
and it will automatically try to correct the situation. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 Version 10.5 might be affected. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 10.5 Fix Pack 9 or later. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT17518 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.10.2016
27.09.2017
27.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
