DB2 FOR LUW / DB2FORLUW / A10 - DB2

When loading data into a table in a DPF environment, i.e. a DPF 
Load, records rejected during partitioning are not counted 
towards the WARNINGCOUNT parameter, so that the load could 
succeed despite some records have been rejected. 
 
Example: 
$ db2 LOAD FROM in.del of DEL WARNINGCOUNT 1 MESSAGES msg.out 
REPLACE INTO dummy PARTITIONED DB CONFIG PARTITIONING_DBPARTNUMS 
\(0,1\) 
 
  Agent Type     Node     SQL Code     Result 
________________________________________________________________ 
______________ 
  LOAD           000      +00000000    Success. 
________________________________________________________________ 
______________ 
  LOAD           001      +00000000    Success. 
________________________________________________________________ 
______________ 
  PARTITION      000      +00000000    Success. 
________________________________________________________________ 
______________ 
  PARTITION      001      +00003107    Success. 
________________________________________________________________ 
______________ 
  PRE_PARTITION  000      +00000000    Success. 
________________________________________________________________ 
______________ 
  RESULTS:       2 of 2 LOADs completed successfully. 
________________________________________________________________ 
______________ 
 
Summary of Partitioning Agents: 
Rows Read                   = 12 
Rows Rejected               = 1 
Rows Partitioned            = 11 
 
Summary of LOAD Agents: 
Number of rows read         = 11 
Number of rows skipped      = 0 
Number of rows loaded       = 11 
Number of rows rejected     = 0 
Number of rows deleted      = 0 
Number of rows committed    = 11 
 
SQL3107W  At least one warning message was encountered during 
LOAD processing.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 3                   * 
****************************************************************

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
 

Problem was first fixed in DB2 Version 10.1 and Fix Pack 3

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC95206 IC95421 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

12.06.2013
27.09.2013
27.09.2013