|
Problem IT41757
|
Status: Closed |
DB2 TRAPS IN MON_GET_PKG_CACHE_STMT ON WINDOWS
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When MON_GET_PKG_CACHE_STMT is called on a Db2 instance running
on Windows, it is possible that Db2 might trap while building
the XML document passed back in the
MAX_COORD_STMT_EXEC_TIME_ARGS column. When Db2 traps messages
may not be written to the db2diag.log, nor may there be any FODC
directory generated. But there may be a message in the Windows
Event Viewer indicating the Db2 service terminated unexpectedly. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Anybody using MON_GET_PKG_CACHE_STMT in a Windows *
* environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Move up to Db2 V11.5 *
**************************************************************** |
| Local Fix: |
Please set the following registry variable:
db2set
db2_system_monitor_settings=DISABLE_MAX_COORD_STMT_EXEC_TIME:tru
e
This can be dynamically set. When this registry variable is set
MON_GET_PKG_CACHE_STMT won't report data for these 3 columns for
new statements added to the package cache:
- MAX_COORD_STMT_EXEC_TIME
- MAX_COORD_STMT_EXEC_TIMESTAMP
- MAX_COORD_STMT_EXEC_TIME_ARGS |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Anybody using MON_GET_PKG_CACHE_STMT in a Windows *
* environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Move up to Db2 V11.5 *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.08.2022
18.08.2022
18.08.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
