|
Problem IC93013
|
Status: Closed |
LOAD: RECORDS REJECTED DURING PARTITIONING ARE NOT COUNTED TOWARDS WARNINGCOUNT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DPF *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 and Fix Pack 3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 and Fix Pack 3 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95206 IC95421
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2013
27.09.2013
27.09.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
