|
Problem IT06049
|
Status: Closed |
DB2 FLIGHT RECORDER TRACE POINT AFFECTS CURSOR LOAD PERFORMANCE |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
A load from cursor might be many times slower compared to
earlier versions due to an incorrectly place DB2 Flight Recorder
trace point.
The Flight recorder trace is designed to be lightweight and
contains valuable diagnostic information, however in this case,
the trace point is called excessively in a performance sensitive
codepath.
To diagnose this problem, take a few repeated stack traces from
the coordinator agent.
When this problem is encountered, the functions at the top of
the stack are :
pdLogEvRecEx
zHandleInterrupt__26sqlucCLoadInterruptHandlerFP16sqlusCBDSChann
eliP5sqlca
iReceiveReplies__16sqlusCBDSChannelFPP17sqluCSerializableUiP21sq
lusCBDSReplyHandlerP22sqlucCInterruptHandlerP5sqlcaP18SQLU_QRY_N
ODE_INFOPs
sqlu_register_table_load
.. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.5 fp6 *
**************************************************************** |
| Local Fix: |
Disabling the event recorder will avoid this problem :
db2pd -db <db> -dmpevrec comp=SQLU name=HIGHFREQ mask=0 |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.12.2014
25.08.2015
03.02.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.6
|
 |
| 10.5.0.7
|
|
