|
Problem IC65152
|
Status: Closed |
LOAD FAILING WITH ERROR SQL2044 (RC=3) |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Intermitted LOAD failures have been experienced. The LOAD job
fails with an SQL2044N error due to failing to write to a
message queue.
The db2diag.log file will show following messages
2009-03-04-06.15.18.209139+000 E69585011A804 LEVEL: Error
(OS)
PID : 4843 TID : 10024 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-9680 APPID:
*LOCAL.db2inst1.090304061823
AUTHID : MISLOAD
EDUID : 10024 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, oper system services, sqlowqueInternal,
probe:40
MESSAGE : ZRC=0x870F0041=-2029060031=SQLO_QUE_NOT_SENT "Message
Not Sent"
DIA8557C No message was sent using the message queue.
CALLED : OS, -, write
OSERR : EAGAIN (11) "Resource temporarily unavailable"
DATA #1 : system V message queue identifier.,
PD_TYPE_SYSV_QUEUE_ID, 4 bytes
0x03400031
DATA #2 : Pointer, 8 bytes
0x9fffffff793f31e0
DATA #3 : unsigned integer, 8 bytes
48
and
2009-03-04-06.15.18.253157+000 I69586368A1011 LEVEL: Error
PID : 4843 TID : 10024 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-9680 APPID:
*LOCAL.db2inst1.090304061823
AUTHID : MISLOAD
EDUID : 10024 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, database utilities, sqluAllocTBufs,
probe:2004
MESSAGE : ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT
"SQLCA has already been built"
DATA #1 : LOADID, PD_TYPE_LOADID, 49 bytes
LOADID: 10024.2009-03-04-06.15.17.829876.0 (8;16)
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2044 sqlerrml: 1
sqlerrmc: 3
sqlerrp : SQLUBUF2
sqlerrd : (1) 0x8015006D (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* Intermitted LOAD failures have been experienced. The *
* LOADjobfails with an SQL2044N error due to failing to write *
* to amessage queue.The db2diag.log file will show following *
* messages2009-03-04-06.15.18.209139+000 E69585011A804 *
* LEVEL:Error(OS)PID : 4843 TID : 10024 *
* PROC :db2sysc0INSTANCE: db2inst1 NODE : 000 *
* DB : SAMPLEAPPHDL : 0-9680 *
* APPID:*LOCAL.db2inst1.090304061823AUTHID : MISLOADEDUID : *
* 10024 EDUNAME: db2agent (SAMPLE) 0FUNCTION: *
* DB2 UDB, oper system services, *
* sqlowqueInternal,probe:40MESSAGE : *
* ZRC=0x870F0041=-2029060031=SQLO_QUE_NOT_SENT"MessageNot *
* Sent"DIA8557C No message was sent using the *
* messagequeue.CALLED : OS, -, writeOSERR : EAGAIN (11) *
* "Resource temporarily unavailable"DATA #1 : system V message *
* queue identifier.,PD_TYPE_SYSV_QUEUE_ID, 4 *
* bytes0x03400031DATA #2 : Pointer, 8 *
* bytes0x9fffffff793f31e0DATA #3 : unsigned integer, 8 *
* bytes48and2009-03-04-06.15.18.253157+000 I69586368A1011 *
* LEVEL:ErrorPID : 4843 TID : 10024 *
* PROC :db2sysc0INSTANCE: db2inst1 NODE : 000 *
* DB : SAMPLEAPPHDL : 0-9680 *
* APPID:*LOCAL.db2inst1.090304061823AUTHID : MISLOADEDUID : *
* 10024 EDUNAME: db2agent (SAMPLE) 0FUNCTION: *
* DB2 UDB, database utilities, *
* sqluAllocTBufs,probe:2004MESSAGE : *
* ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT"SQLCA has already *
* been built"DATA #1 : LOADID, PD_TYPE_LOADID, 49 bytesLOADID: *
* 10024.2009-03-04-06.15.17.829876.0 (8;16)DATA #2 : SQLCA, *
* PD_DB2_TYPE_SQLCA, 136 bytessqlcaid : SQLCA sqlcabc: 136 *
* sqlcode: -2044 sqlerrml: 1sqlerrmc: 3sqlerrp : *
* SQLUBUF2sqlerrd : (1) 0x8015006D (2) 0x00000000 *
* (3)0x00000000(4) 0x00000000 (5) 0x00000000 *
* (6)0x00000000sqlwarn : (1) (2) (3) (4) *
* (5) (6)(7) (8) (9) (10) *
* (11)sqlstate: *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 FP3 *
**************************************************************** |
| Local Fix: |
Monitor message queue usage with 'ipcs' command to see if you ar
e exceeding system wide limits. -
Check your kernel parameter settings (MSGMNB, MSGTQL, MSGMBS) an
d increase them if they are set to low. -
Retry the LOAD command. |
| available fix packs: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 version 9.7 FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.12.2009
27.09.2010
27.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
