|
Problem IC67598
|
Status: Closed |
DB2 LOAD MIGHT CRASH THE DB2 INSTANCE IF THE DB2LRID PROCESS HITS OUT-OF-MEMORY ERROR VERY EARLY ON |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 LOAD might crash the DB2 instance if the db2lrid process
hits out-of-memory error very early on
A DB2 LOAD might crash the DB2 instance if the db2lrid process
hits out-of-memory error very early on. The crashing db2lrid
process' stack trace shows the following functions:
...
sqlpCleanupInDPSOnError
sqluTermRidder
sqlulRIDder
...
(you may see sqluFlushRidderData or something else other than
sqluTermRidder)
Just before the DB2 instance crash, you will see out-of-memory
message similar to the following:
2010-03-26-23.53.36.521823-240 I30956519E550 LEVEL: Error
PID : 16496 TID : 29931 PROC : db2sysc
3
INSTANCE: svtdbm3 NODE : 003 DB : DMFRC1
APPHDL : 1-4399 APPID: *N1.svtdbm3.100327035335
AUTHID : SVTDBM3
EDUID : 29931 EDUNAME: db2lrid 3
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 136 bytes
LOADID: 28303.2010-03-26-23.53.35.700294.1 (9;341)
DB monitor init error: , 0, ffffffff8b0f0002, Detected in
file:sqluedus.C, Line:1543
2010-03-26-23.53.36.529635-240 I31008350E417 LEVEL: Error
PID : 16496 TID : 29931 PROC : db2sysc
3
INSTANCE: svtdbm3 NODE : 003
EDUID : 29931 EDUNAME: db2lrid 3
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 107 bytes
LOADID: 28303.2010-03-26-23.53.35.700294.1 (9;341)
, -1961951230, 0, Detected in file:sqlulrid.C, Line:762
2010-03-26-23.53.46.952063-240 I31043209E422 LEVEL: Warning
PID : 16496 TID : 29931 PROC : db2sysc
3
INSTANCE: svtdbm3 NODE : 003
EDUID : 29931 EDUNAME: db2lrid 3
FUNCTION: DB2 UDB, RAS/PD component,
pdEDUIsInDB2KernelOperation, probe:600
DATA #1 : String, 63 bytes
FFFFFD7FFAF29A54 __1cXsqlpCleanupInDPSOnError6FpnIsqeAgent__v_
DATA #2 : String, 4 bytes
sqlp
2010-03-26-23.53.46.961052-240 I31043632E447 LEVEL: Severe
PID : 16496 TID : 29931 PROC : db2sysc
3
INSTANCE: svtdbm3 NODE : 003
EDUID : 29931 EDUNAME: db2lrid 3
FUNCTION: DB2 UDB, RAS/PD component,
pdResilienceIsSafeToSustain, probe:800
DATA #1 : String, 37 bytes
Trap Sustainability Criteria Checking
DATA #2 : Hex integer, 8 bytes
0x200000000000880D
DATA #3 : Boolean, 1 bytes
false
2010-03-26-23.53.47.049297-240 I31044080E394 LEVEL: Event
PID : 16496 TID : 29931 PROC : db2sysc
3
INSTANCE: svtdbm3 NODE : 003
EDUID : 29931 EDUNAME: db2lrid 3
FUNCTION: DB2 UDB, trace services, pdInvokeCalloutScript,
probe:10
START : Invoking /home/svtdbm3/sqllib/bin/db2cos_trap from
oper system services sqloEDUCodeTrapHandler |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* A DB2 LOAD might crash the DB2 instance if the db2lrid *
* process hits out-of-memory error very early on. The *
* crashing db2lrid process' stack trace shows the following *
* functions: *
* *
* ... *
* sqlpCleanupInDPSOnError *
* sqluTermRidder *
* sqlulRIDder *
* ... *
* *
* (you may see sqluFlushRidderData or something else other *
* than sqluTermRidder) *
* *
* *
* Just before the DB2 instance crash, you will see *
* out-of-memory message similar to the following: *
* *
* 2010-03-26-23.53.36.521823-240 I30956519E550 LEVEL: *
* Error *
* PID : 16496 TID : 29931 PROC : *
* db2sysc 3 *
* INSTANCE: svtdbm3 NODE : 003 DB : *
* DMFRC1 *
* APPHDL : 1-4399 APPID: *
* *N1.svtdbm3.100327035335 *
* AUTHID : SVTDBM3 *
* EDUID : 29931 EDUNAME: db2lrid 3 *
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 *
* DATA #1 : String, 136 bytes *
* LOADID: 28303.2010-03-26-23.53.35.700294.1 (9;341) *
* DB monitor init error: , 0, ffffffff8b0f0002, Detected in *
* file:sqluedus.C, Line:1543 *
* *
* 2010-03-26-23.53.36.529635-240 I31008350E417 LEVEL: *
* Error *
* PID : 16496 TID : 29931 PROC : *
* db2sysc 3 *
* INSTANCE: svtdbm3 NODE : 003 *
* EDUID : 29931 EDUNAME: db2lrid 3 *
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 *
* DATA #1 : String, 107 bytes *
* LOADID: 28303.2010-03-26-23.53.35.700294.1 (9;341) *
* , -1961951230, 0, Detected in file:sqlulrid.C, Line:762 *
* *
* 2010-03-26-23.53.46.952063-240 I31043209E422 LEVEL: *
* Warning *
* PID : 16496 TID : 29931 PROC : *
* db2sysc 3 *
* INSTANCE: svtdbm3 NODE : 003 *
* EDUID : 29931 EDUNAME: db2lrid 3 *
* FUNCTION: DB2 UDB, RAS/PD component, *
* pdEDUIsInDB2KernelOperation, probe:600 *
* DATA #1 : String, 63 bytes *
* FFFFFD7FFAF29A54 *
* __1cXsqlpCleanupInDPSOnError6FpnIsqeAgent__v_ *
* DATA #2 : String, 4 bytes *
* sqlp *
* *
* 2010-03-26-23.53.46.961052-240 I31043632E447 LEVEL: *
* Severe *
* PID : 16496 TID : 29931 PROC : *
* db2sysc 3 *
* INSTANCE: svtdbm3 NODE : 003 *
* EDUID : 29931 EDUNAME: db2lrid 3 *
* FUNCTION: DB2 UDB, RAS/PD component, *
* pdResilienceIsSafeToSustain, probe:800 *
* DATA #1 : String, 37 bytes *
* Trap Sustainability Criteria Checking *
* DATA #2 : Hex integer, 8 bytes *
* 0x200000000000880D *
* DATA #3 : Boolean, 1 bytes *
* false *
* *
* 2010-03-26-23.53.47.049297-240 I31044080E394 LEVEL: *
* Event *
* PID : 16496 TID : 29931 PROC : *
* db2sysc 3 *
* INSTANCE: svtdbm3 NODE : 003 *
* EDUID : 29931 EDUNAME: db2lrid 3 *
* FUNCTION: DB2 UDB, trace services, pdInvokeCalloutScript, *
* probe:10 *
* START : Invoking /home/svtdbm3/sqllib/bin/db2cos_trap from *
* oper system services sqloEDUCodeTrapHandler *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
Configure the DB2 system appropriately according to the system
workload, to avoid having LOAD operations encountering
out-of-memory situation. |
| 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 DB2 Version 9.7 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67602
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.04.2010
26.04.2010
26.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
|
 |
