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

DB2 MAY ABNORMALLY TERMINATE WHEN USING CLI LOAD

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
When using CLI LOAD (array inserts using LOAD) into a table 
containing an implicitly hidden row change timestamp column, DB2 
may terminate abnormally with the following callstack i.e. 
 
 
Stack #1    Signal #11     Timestamp 2011-05-10-13.36.52.163484 
 
0        ossDumpStackTraceEx 
1        OSSTrapFile::dumpEx 
2        OSSTrapFile::dump 
3        sqlo_trce 
4        sqloEDUCodeTrapHandler 
5        __invoke_dynamic_linker 
6        sqluCliCheckBniValues 
7        sqlrr_array_input_load 
8        sqljs_ddm_excsqlstt 
9        sqljsParseRdbAccessed 
10       sqljsParse 
11       sqljsSqlam 
12       sqljsDriveRequests 
13       sqljsDrdaAsInnerDriver 
14       sqljsDrdaAsDriver 
15       sqeAgent::RunEDU 
16       sqzEDUObj::EDUDriver 
17       sqlzRunEDU 
18       sqloEDUEntry 
19       pthread_cond_timedwait@@GLIBC_2.3.2 
20       clone 
 
 
The function sqluCliCheckBniValues is indicative of this apar 
being hit.  This APAR is hit only if the following are true: 
 
o Target table contains an implicitly hidden row change 
  timestamp column 
 
o The insert statement used for cli load does not contain a 
  target column list.  For example: insert into t1 values(?)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.8 Fix Pack 5.                   * 
****************************************************************
Local Fix:
Use a target column list in the insert statement. For example: 
insert into t1(c1) values(?)
Solution
Problem was first fixed in DB2 LUW Version 9.8 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.04.2012
12.07.2012
12.07.2012
Problem solved at the following versions (IBM BugInfos)
9.8.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.5 FixList