|
Problem IC67118
|
Status: Closed |
A CLIENT PROCESS RUNNING IMPORT OPERATION MIGHT CRASH IF IT RUNS INTO OUT-OF-MEMORY ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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.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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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. At a
minimum, this fix should be applied on the client. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67138
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.03.2010
08.04.2010
08.04.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
|
 |
