|
Problem IT19962
|
Status: Closed |
SLOW PERFORMANCE WHEN MONITORING SQL ROUTINES |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When MON_RTN_EXECLIST = ON, there may be slow performance
running SQL routines. Diagnostics will show contention on the
SQLO_LT_sqmRtnMetricsNode__m_metricsLatch latch. One agent will
be holding the latch and have a stack similar to the following:
sqzChainedHashTableTpl<sqlra_executable_id,
sqmExecListEntryNode, sqmExecListManagerHash>
sqmRtnMetricsNode::findOrCreateStmt
sqmRtnMetricsNode::rollupMetricsForStmt
sqlmTermActivityMetrics
sqlrr_remove_curr_activity
sqlrr_activity_exe_stop_common
sqlrr_activity_exe_stop
sqlricls_complex
sqlriecc
:
Other agents will be waiting for the latch and have a stack
similar to the following:
sqmRtnMetricsNode::latchMetrics
sqlmTermActivityMetrics
sqlrr_activity_exe_stop
sqlricls_complex
sqlriecc
: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* When mon_rtn_execlist=on and SQL routines frequently called. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply v11.1 Mod 1 Fixpack 2 to DB2 server *
**************************************************************** |
| Local Fix: |
SET DB CFG mon_rtn_execlist=off |
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in v11.1 Mod 1 Fixpack 2. |
| Workaround |
See LOCAL FIX. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.03.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
