home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC82263 Status: Closed

WINDOWS: DB2SUPPORT MAY RECORD A NEGATIVE VALUE FOR "TOTAL AVAILABLE
VIRTUAL MEMORY IN BYTES" IN MEMUSAGE.OUT.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
On computers with more than 4 GB of memory, db2support may 
record a negative value for "Total available virtual memory in 
bytes" in memusage.out, due to the known issue of 
GlobalMemoryStatus function. 
 
memusage.out 
=============================================================== 
Memory Usage Info 
 
Total available virtual memory in bytes         = -136343552 
===============================================================
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 FixPack 10.                           * 
****************************************************************
Local Fix:
Not available.
Solution
Problem was first fixed in DB2 UDB Version 9.5 FixPack 10.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC82295 IC87880 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.03.2012
21.08.2012
21.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList