|
Problem IC63099
|
Status: Closed |
db2exfmt outputs HEAPUSE : (Maximum Statement Heap Usage) |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2exfmt outputs HEAPUSE : (Maximum Statement Heap Usage)
when the memory size is greater than 2GB, we see a negative
number.
It has platform-dependent behaviour. On AIX, there is negative
number.
Arguments:
---------
BLDLEVEL: (Build level)
DB2 v9.5.0.4 : s090429
HEAPUSE : (Maximum Statement Heap Usage)
-190800 Pages
On linuxamd64, the behaviour is different. Instead of a negative
number, db2exfmt outputs an extreamly large number
Arguments:
---------
BLDLEVEL: (Build level)
DB2 v9.5.0.4 : s090429
HEAPUSE : (Maximum Statement Heap Usage)
4503599626995952 Pages
The wrong "HEAPUSE" info is stored in the EXPLAIN tables, any
program that queries the explain tables may see the incorrect
HEAPUSE. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* It has platform-dependent behaviour *
****************************************************************
* PROBLEM DESCRIPTION: *
* db2exfmt outputs HEAPUSE : (Maximum Statement Heap *
* Usage)when the memory size is greater than 2GB, we see a *
* negativenumber.It has platform-dependent behaviour. On AIX, *
* there isnegative number.Arguments:---------BLDLEVEL: (Build *
* level)DB2 v9.5.0.4 : s090429HEAPUSE : (Maximum Statement *
* Heap Usage)-190800 PagesOn linuxamd64, the behaviour is *
* different. Instead of anegative number, db2exfmt outputs an *
* extreamly large numberArguments:---------BLDLEVEL: (Build *
* level)DB2 v9.5.0.4 : s090429HEAPUSE : (Maximum Statement *
* Heap Usage)4503599626995952 PagesThe wrong "HEAPUSE" info is *
* stored in the EXPLAIN tables,any program that queries the *
* explain tables may see theincorrect HEAPUSE. *
****************************************************************
* RECOMMENDATION: *
* upgrade to Version 9.7 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.09.2009
10.06.2010
10.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
