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 IC67138 Status: Closed

A CLIENT PROCESS RUNNING IMPORT OPERATION MIGHT CRASH IF IT RUNS INTO
OUT-OF-MEMORY ERROR

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
A client process running IMPORT operation might crash if it runs 
into out-of-memory error.  You will see an entry in db2diag.log 
similar to the following: 
 
2009-09-30-02.26.32.404266-240 E73256E601 LEVEL: Warning 
PID : 20395 TID : 47742401386944PROC : db2bp 
INSTANCE: regress NODE : 257 
APPID : *LOCAL.regress.090930062629 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloMemLogPoolConditions, probe:30 
DATA #1 : <preformatted> 
Out of memory failure for Application Heap (APPLHEAPSZ). 
Requested block size : 819782 bytes. 
Physical heap size : 23396352 bytes. 
Configured heap size : 1310720000 bytes. 
Unreserved memory used by heap : 0 bytes. 
Unreserved memory left in set : 0 bytes. 
 
Note that this problem only occurs in rare, specific 
circumstances; most of the time IMPORT returns an appropriate 
error when it hits out-of-memory error.  Also note that it is 
only the client process running the IMPORT operation that 
crashes; the DB2 instance is not affected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A client process running IMPORT operation might crash if it  * 
* runs into out-of-memory error.  You will see an entry in     * 
* db2diag.log similar to the following:                        * 
*                                                              * 
* 2009-09-30-02.26.32.404266-240 E73256E601 LEVEL: Warning     * 
* PID : 20395 TID : 47742401386944PROC : db2bp                 * 
* INSTANCE: regress NODE : 257                                 * 
* APPID : *LOCAL.regress.090930062629                          * 
* FUNCTION: DB2 UDB, SQO Memory Management,                    * 
* sqloMemLogPoolConditions, probe:30                           * 
* DATA #1 : <preformatted>                                     * 
* Out of memory failure for Application Heap (APPLHEAPSZ).     * 
* Requested block size : 819782 bytes.                         * 
* Physical heap size : 23396352 bytes.                         * 
* Configured heap size : 1310720000 bytes.                     * 
* Unreserved memory used by heap : 0 bytes.                    * 
* Unreserved memory left in set : 0 bytes.                     * 
*                                                              * 
* Note that this problem only occurs in rare, specific         * 
* circumstances; most of the time IMPORT returns an            * 
* appropriate error when it hits out-of-memory error.  Also    * 
* note that it is only the client process running the IMPORT   * 
* operation that crashes; the DB2 instance is not affected.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8 Fix Pack 3.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem was first fixed in Version 9.8 Fix Pack 3.  At a 
minimum, this fix should be applied on the client.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.03.2010
20.12.2010
20.12.2010
Problem solved at the following versions (IBM BugInfos)
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList