|
Problem IC91495
|
Status: Closed |
ACTIVITYSTMT TABLE OF ACTIVITIES EVENT MONITOR DOES NOT CAPTURE SQL STATEMENTS COMPILED USING THE REOPT ALWAYS BIND OPTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When an activities event monitor is active and detailed activity
collection is enabled through a COLLECT ACTIVITY DATA WITH
DETAILS clause on a WLM object, the ACTIVITYSTMT table does not
capture SQL statements compiled using the REOPT ALWAYS bind
option. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to v10.1 Fix Pack 3 *
**************************************************************** |
| Local Fix: |
Rebind the SQL statement with the option REOPT ONCE. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in v10.1 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.04.2013
01.10.2013
01.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
