|
Problem IC64017
|
Status: Closed |
LOAD HANG WITH "CREATING LOAD LIST ELEMENT , -1961951230" IN DB2DIAG.LOG. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When a LOAD fails with "Creating load list element ,
-1961951230" in db2diag.log, all subsequent LOADs will probably
hang in the stage of "Init SA is running". IMPORT and some SQL
operations/queries to the same table where a LOAD is hanging
will also hang.
Here is the error message in db2diag.log for your reference:
============================================
2009-04-05-19.27.01.667899+480 I14280042641A490 LEVEL: Error
PID : 11486 TID : 1 PROC :
db2linit 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-1715 APPID:
10.154.145.29.63342.09040508375
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 140 bytes
LOADID: 17945.2009-04-05-19.27.01.636544.0 (4;10418)
Allocate memory for create , 0, 0000000000000000, Detected in
file:sqlullst.C, Line:276
2009-04-05-19.27.01.668029+480 I14280043132A501 LEVEL: Error
PID : 11486 TID : 1 PROC :
db2linit 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-1715 APPID:
10.154.145.29.63342.09040508375
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 151 bytes
LOADID: 17945.2009-04-05-19.27.01.636544.0 (4;10418)
Creating load list element , -1961951230, 0000000000000000,
Detected in file:sqluvtl2.C, Line:2075
...
2009-04-05-19.27.48.756931+480 I14280997330A326 LEVEL: Severe
PID : 11486 TID : 1 PROC :
db2agent (idle) 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services,
sqloDumpLatchTableToLog, probe:10
MESSAGE : Latch leaked on EDU termination: File sqlullst.C :
Line 269
============================================
PLEASE NOTE that the error message "Latch leaked on EDU
termination:" may or may not present. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* LOAD HANG WITH "CREATING LOAD LIST ELEMENT , -1961951230" IN *
* DB2DIAG.LOG. *
* *
* When a LOAD fails with "Creating load list element , *
* -1961951230" in db2diag.log, all subsequent LOADs will *
* probably hang in the stage of "Init SA is running". IMPORT *
* and some SQL operations/queries to the same table where a *
* LOAD is hanging will also hang. *
* *
* Here is the error message in db2diag.log for your reference: *
* ============================================ *
* 2009-04-05-19.27.01.667899+480 I14280042641A490 LEVEL: *
* Error *
* PID : 11486 TID : 1 PROC : *
* db2linit 0 *
* INSTANCE: db2inst1 NODE : 000 *
* APPHDL : 0-1715 APPID: *
* 10.154.145.29.63342.09040508375 *
* AUTHID : DB2INST1 *
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 *
* DATA #1 : String, 140 bytes *
* LOADID: 17945.2009-04-05-19.27.01.636544.0 (4;10418) *
* Allocate memory for create , 0, 0000000000000000, Detected *
* in *
* file:sqlullst.C, Line:276 *
* *
* 2009-04-05-19.27.01.668029+480 I14280043132A501 LEVEL: *
* Error *
* PID : 11486 TID : 1 PROC : *
* db2linit 0 *
* INSTANCE: db2inst1 NODE : 000 *
* APPHDL : 0-1715 APPID: *
* 10.154.145.29.63342.09040508375 *
* AUTHID : DB2INST1 *
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 *
* DATA #1 : String, 151 bytes *
* LOADID: 17945.2009-04-05-19.27.01.636544.0 (4;10418) *
* Creating load list element , -1961951230, 0000000000000000, *
* Detected in file:sqluvtl2.C, Line:2075 *
* ... *
* *
* 2009-04-05-19.27.48.756931+480 I14280997330A326 LEVEL: *
* Severe *
* PID : 11486 TID : 1 PROC : *
* db2agent (idle) 0 *
* INSTANCE: db2inst1 NODE : 000 *
* FUNCTION: DB2 UDB, oper system services, *
* sqloDumpLatchTableToLog, probe:10 *
* MESSAGE : Latch leaked on EDU termination: File sqlullst.C : *
* Line 269 *
* ============================================ *
* PLEASE NOTE that the error message "Latch leaked on EDU *
* termination:" may or may not present. *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to v97 fixpack 1 or later. *
**************************************************************** |
| Local Fix: |
Increase database heap size (DBHEAP db config parameter) to
avoid running out of database heap memory, which will avoid
hitting this problem. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 |
This problem is first fixed in version 9.7 fixpack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
23.02.2010
23.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
