|
Problem IC77532
|
Status: Closed |
MONITOR STMT FIELDS ARE BIENG UNINTENTIONALLY RESET TO ZERO IN A PARTICULAR CASE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When an application is bieng monitored , stmt fields of an
application are bieng reset to zero when you open a
new cursor.
This can happen when
you open cursor1 for a table , then do some fetches
then if you later open another cursor2 the stmt field
such as rows_read , rows_written will be reset to zero
for cursor1. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* See APAR Description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP5. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
V9.7 FP5 will contain the fix. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.07.2011
22.12.2011
22.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
