DB2 - Problem description
Problem IT20501 | Status: Closed |
INTERMITTENT LOAD ABNORMAL END IN THE BUILD PHASE: UNEXPECTED MSG. , 28, 0, DETECTED IN FILE:SQLUVLD.C, LINE:5506 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
A LOAD job can unexpectedly end with issue raised on build phase of the LOAD reporting "Unexpected msg. , 28, 0, Detected in file:sqluvld.C, Line:5506". Issuing the same job a second time most often succeed. Symptoms in db2diag.log : 2017-03-29-22.03.49.137730+000 I30026460A575 LEVEL: Warning PID : 12648892 TID : 43353 PROC : db2sysc 1 INSTANCE: xxxxxx NODE : 001 DB : xxxxx APPHDL : 0-24524 APPID: xxx.xx.xxx.152.33465.170329215211 AUTHID : xxxxxx HOSTNAME: xxxxxxxx EDUID : 43353 EDUNAME: db2lrid0 1 FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:315 DATA #1 : String, 104 bytes LOADID: 40662.2017-03-29-21.52.11.535870.0 (32;26) Starting BUILD phase at 03/29/2017 22:03:49.134619. 2017-03-29-22.03.49.144039+000 I30027036A582 LEVEL: Error PID : 12648892 TID : 73769 PROC : db2sysc 1 INSTANCE: xxxxxx NODE : 001 DB : xxxxxx APPHDL : 0-24524 APPID: xxx.x.xxx.152.33465.170329215211 AUTHID : xxxxxxxx HOSTNAME: kfdcpu02 EDUID : 73769 EDUNAME: db2lload 1 FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, probe:0 DATA #1 : String, 113 bytes LOADID: 40662.2017-03-29-21.52.11.535870.0 (32;26) Unexpected msg. , 28, 0, Detected in file:sqluvld.C, Line:5506 2017-03-29-22.03.49.145281+000 I30027619A1046 LEVEL: Error PID : 12648892 TID : 73769 PROC : db2sysc 1 INSTANCE: xxxxxx NODE : 001 DB : xxxxxx APPHDL : 0-24524 APPID: xxx.x.xxx.152.33465.170329215211 AUTHID : xxxxxxxx HOSTNAME: xxxxxxxx EDUID : 73769 EDUNAME: db2lload 1 FUNCTION: DB2 UDB, database utilities, sqlulFRMResponse, probe:5509 MESSAGE : ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT "SQLCA has already been built" DATA #1 : LOADID, PD_TYPE_LOADID, 50 bytes LOADID: 40662.2017-03-29-21.52.11.535870.0 (32;26) DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2044 sqlerrml: 1 sqlerrmc: 4 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: 2017-03-29-22.03.49.147511+000 I30028666A537 LEVEL: Severe PID : 12648892 TID : 73769 PROC : db2sysc 1 INSTANCE: xxxxxx NODE : 001 DB : xxxxxx APPHDL : 0-24524 APPID: xxx.x.xxx.152.33465.170329215211 AUTHID : xxxxxxxx HOSTNAME: xxxxxxxx EDUID : 73769 EDUNAME: db2lload 1 FUNCTION: DB2 UDB, database utilities, sqlulFRMResponse, probe:5509 MESSAGE : DIA0001E An internal error occurred. Report the following error code : "". 2017-03-29-22.03.49.148644+000 I30029204A573 LEVEL: Severe PID : 12648892 TID : 73769 PROC : db2sysc 1 INSTANCE: xxxxxx NODE : 001 DB : xxxxxxxx APPHDL : 0-24524 APPID: xxx.x.xxx.152.33465.170329215211 AUTHID : xxxxxxxx HOSTNAME: xxxxxxx EDUID : 73769 EDUNAME: db2lload 1 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging function), probe:50 MESSAGE : rc DATA #1 : Hexdump, 4 bytes 0x0A000000C4BFBC28 : 0000 0000 .... 2017-03-29-22.03.49.149623+000 I30029778A180 LEVEL: Severe PID:12648892 TID:73769 NODE:001 Title: commacb Dump File:/db2fs/xxxxxx/NODE0001/db2dump/12648892.73769.001.dump.bin 2017-03-29-22.03.49.151080+000 I30029959A180 LEVEL: Severe PID:12648892 TID:73769 NODE:001 Title: loadacb Dump File:/db2fs/xxxxxx/NODE0001/db2dump/12648892.73769.001.dump.bin | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Using LOAD command * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.5 fix pack 10 or up * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : follow-up : IT23141 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.05.2017 16.07.2018 16.07.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |