DB2 - Problem description
| Problem IC68642 | Status: Closed |
CALL OF A PROCEDURE OR REFERENCE TO A FUNCTION DEFINED WITHIN A MODULE WILL CAUSE A RECOMPILE RATHER THAN A PACKAGE CACHE HIT. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
If a user has been granted execute on a module, each CALL of a procedure within the module or reference to a FUNCTION within the module will cause a recompile of the CALL statement, Aside from the extra compiles this causes, this may result in a series of valid entries in the package cache (one per statement with a MODULE procedure or funtion reference), and eventually searching these entries can cause severe performance problems | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * users of MODULES or SQL/PL PACKAGES * **************************************************************** * PROBLEM DESCRIPTION: * * Performance impacted when module procedures/functions are * * used in dynamic SQL. * **************************************************************** * RECOMMENDATION: * * Upgrade to V97 fixpack 3 * **************************************************************** | |
| Local Fix: | |
Granting the user EXECUTE on procedures and functions while
unnecessary for authorization can avoid the extra compiles.
Since execute privilege cannot be granted directly on a
procedure or function within a module, this would have to be
done using the wildcard specification ("GRANT EXECUTE ON
PROCEDURE/FUNCTION <SCHEMA>.* to ....") | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Fixed in v97 fixpack 3 | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC70184 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.05.2010 23.09.2010 23.09.2010 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.3 |
|
| 9.7.0.3 |
|