|
Problem IC77381
|
Status: Closed |
WITH THRESHOLD VIOLATION EVENT MONITOR AND A LOT THRESHOLD VIOLATION, THERE CAN BE A PERFORMANCE IMPACT DUE TO LATCHING |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When you turned on threshold violation event monitor and
there are a lot threshold violation happening, you may
experience performance slowdown with below latch waitings
db2pd -latches:
Database Partition 0 -- Active -- Up 0 days 02:51:48 -- Date
06/21/2011 15:02:24
Latches:
Address Holder Waiter Filename
LOC LatchType
No latch holders.
...
0xC0000015B45E2380 0 73 Unknown
9995 SQLO_LT_sqlrwQueueLatch__queueLatch
0xC0000015B45E2380 0 81 Unknown
9995 SQLO_LT_sqlrwQueueLatch__queueLatch
0xC0000015B45E2380 0 82 Unknown
9995 SQLO_LT_sqlrwQueueLatch__queueLatch
0xC0000015B45E2380 0 86 Unknown
9995 SQLO_LT_sqlrwQueueLatch__queueLatch
0xC0000015B45E2380 0 87 Unknown
9995 SQLO_LT_sqlrwQueueLatch__queueLatch
0xC0000015B45E2380 0 92 Unknown
9995 SQLO_LT_sqlrwQueueLatch__queueLatch
0xC0000015B45E2380 0 104 Unknown
9995 SQLO_LT_sqlrwQueueLatch__queueLatch
...
and may associated with below call stack:
0: c000000001d521d0 : sched_yield() + 0x30
(/usr/lib/hpux64/librt.so.1)
1: c000000032bb8b40 : sqloSpinLockConflict() + 0x2d0
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
2: c000000038bad6f0 :
_Z14sqloxltc_trackP11sqlo_xlatchPKcmP16SQLO_LATCH_TABLEb14SQLO_L
T_VALUES() + 0xd0 (/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
3: c000000038be0930 :
_Z26sqlrwObtainThresholdTicketP8sqlrr_cbP18sqlrw_threshold_cbP27
sqlrw_activity_threshold_cb() + 0x160
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e
.so)
4: c000000038bdfff0 :
_Z41sqlrwPassQueuingThresholdsAtQueueLocationP8sqlrr_cbP27sqlrw_
activity_threshold_cbP31sqlrw_threshold_activity_ticketii() +
0x7a0 (/opt/IBM/d
b2/V97fp4S_26864/lib64/libdb2e.so)
5: c000000038bdd6d0 :
_Z39sqlrwPassDBConcurrencyQueuingThresholdsP8sqlrr_cbP19sqlrr_cu
rr_activity() + 0x3e0
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
6: c000000038bef290 :
_Z43sqlrwProcessThresholdsBeforeRunningActivityP8sqlrr_cbP19sqlr
r_curr_activity() + 0x1710
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
7: c00000003308d400 :
_Z37sqlrr_activity_exe_start_common_coordP8sqlrr_cbiPP19sqlrr_cu
rr_activityPi() + 0x28c0
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
8: c000000032ccaed0 :
_Z24sqlrr_activity_exe_startP8sqlrr_cbPi() + 0x990
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
9: c000000032bf96c0 :
_Z26sqlrr_process_open_requestP8sqlrr_cbPbPmP15db2UCCursorInfoS1
_() + 0xf10 (/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
10: c000000032c573f0 :
_Z10sqlrr_openP14db2UCinterfaceP15db2UCCursorInfo() + 0x2f0
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
11: c000000032bf4be0 :
_Z16sqljs_ddm_opnqryP14db2UCinterfaceP13sqljDDMObject() + 0x7c0
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
12: c000000032ca04e0 :
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface() + 0x220
(/opt/IBM/db2/V97fp4S_26864/lib64/libdb2e.so)
An example for enbaled threshold violation event monitor is:
CREATE EVENT MONITOR DB2THRESHOLDVIOLATIONS
FOR THRESHOLD VIOLATIONS
WRITE TO TABLE
THRESHOLDVIOLATIONS (TABLE
THRESHOLDVIOLATIONS_DB2THRESHOLDVIOLATIONS
IN USERSPACE1
PCTDEACTIVATE 100),
CONTROL (TABLE CONTROL_DB2THRESHOLDVIOLATIONS
IN USERSPACE1
PCTDEACTIVATE 100)
AUTOSTART; |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* see ERROR DESCRIPTION *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Turn off threshold event monitor. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.07.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
