DB2 - Problem description
Problem IT01013 | Status: Closed |
DB2 LOAD COMMAND PRODUCES 'ERROR' MESSAGES DURING SUCCESSFUL OPERATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
While performing a LOAD the following messages will be logged in the db2diag.log file: 2014-04-10-12.09.15.239015+060 I1039198E772 LEVEL: Error PID : 17847 TID : 139787134560000 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : COLUMN APPHDL : 0-158 APPID: *LOCAL.db2inst1.140410094411 AUTHID : DB2INST1 HOSTNAME: db2blu.db2.local EDUID : 80 EDUNAME: db2agent (COLUMN) 0 FUNCTION: DB2 UDB, database utilities, sqluCalcCDELoadMemory, probe:1593 DATA #1 : LOADID, PD_TYPE_LOADID, 45 bytes LOADID: 80.2014-04-10-12.09.14.767619.0 (2;5) DATA #2 : String, 193 bytes CDE LOAD (1 cpu, 1 tuple fmt, 1 column fmt, 1 bm, 7 table cg, 9 synopsis cg) Memory (MB): LOAD 12 available, 2 minimum, 1 writer, 2 extent, 5 tuple, 12 total. HISTOGRAM 46 available, 0 minimum. 2014-04-10-12.09.15.240662+060 I1040537E662 LEVEL: Error PID : 17847 TID : 139787134560000 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : COLUMN APPHDL : 0-158 APPID: *LOCAL.db2inst1.140410094411 AUTHID : DB2INST1 HOSTNAME: db2blu.db2.local EDUID : 80 EDUNAME: db2agent (COLUMN) 0 FUNCTION: DB2 UDB, database utilities, sqluAllocTBufs, probe:2472 DATA #1 : LOADID, PD_TYPE_LOADID, 45 bytes LOADID: 80.2014-04-10-12.09.14.767619.0 (2;5) DATA #2 : String, 91 bytes LOAD Buffer Allocation: number 26 5 26, sizes 68 64 (1176) 132 (KB), split watermarks 4 13. 2014-04-10-12.09.17.720420+060 I1061468E598 LEVEL: Error PID : 17847 TID : 139787071645440 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : COLUMN APPHDL : 0-158 APPID: *LOCAL.db2inst1.140410094411 AUTHID : DB2INST1 HOSTNAME: db2blu.db2.local EDUID : 100 EDUNAME: db2lcfm0 0 FUNCTION: DB2 UDB, database utilities, squRebuildIndexes, probe:1821 DATA #1 : LOADID, PD_TYPE_LOADID, 45 bytes LOADID: 80.2014-04-10-12.09.14.767619.0 (2;5) DATA #2 : String, 33 bytes Rebuilding CDE Index: 4, 2, 1, 1. Even when the LOAD completes successfully these messages are still logged. Customers who have reports sent based on 'Error' messages logged in the db2diag.log file will then be incorrectly notified of a problem. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 Version 10.5 Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.04.2014 08.09.2014 08.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |