DB2 - Problem description
Problem IC64625 | Status: Closed |
USE OF MON_GET_PKG_CACHE_STMT MONITORING TABLE FUNCTION MAY RESULT IN ABNORMAL TERMINATION OF THE DATABASE SERVER. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
A timing condition exists in the MON_GET_PKG_CACHE_STMT monitoring table function. Under certain circumstances, the table function may access an invalid piece of memory and abnormally terminate the database server. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Any users issuing the MON_GET_PKG_CACHE_STMT table function. * **************************************************************** * PROBLEM DESCRIPTION: * * The database server may abnormally terminate when using the * * MON_GET_PKG_CACHE_STMT table function. The termination is * * due to an unsafe memory access and is timing related. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 fix pack 1. * **************************************************************** | |
Local Fix: | |
There is no local work around. Any use of the MON_GET_PKG_CACHE_STMT table function is subject to this timing condition. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
This problem is fixed in DB2 Version 9.7 fix pack 1. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.11.2009 14.01.2010 14.01.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |