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

LOAD JOB FAILS WITH ERROR MESSAGE SQL2044 RC=1 ON THE WINDOWS PLATFORM.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The load job fails  with sql2044 rc=1 on the windows platform. 
You may see the following message in the db2diag.log file. 
 
 2011-03-13-10.52.25.312000-300 I29566014F1032     LEVEL: Error 
PID     : 5432                 TID  : 2444        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 001         DB   : SAMPLE 
APPHDL  : 0-6170               APPID: 
10.30.10.25.19462.110313154947 
AUTHID  : db2inst1 
EDUID   : 2444                 EDUNAME: db2lload 1 
FUNCTION: DB2 UDB, database utilities, sqluCreateMsgQueue, 
probe:15478 
MESSAGE : ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : LOADID, PD_TYPE_LOADID, 49 bytes 
LOADID: 5968.2011-03-13-10.52.22.831000.0 (274;7) 
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -2044   sqlerrml: 1 
 sqlerrmc: 1 
 sqlerrp : SQLUVLD 
 sqlerrd : (1) 0x8015006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000001 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
If the db2 trace is taken the SQLO_QUE_DUP token  will be dumped 
into the formatted trace file. 
sqloMLNique exit [rc = 0x870F003D = -2029060035 = SQLO_QUE_DUP]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all users running LOAD on Windows platforms                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2012
01.11.2012
01.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList