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

REMOVE DIAG MESSAGE "ROW HASH MISMATCH" WHEN LOAD ASKED TO DISCARD SUCH
ROWS ON V11.5

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
When the user uses the following command to perform load
operation, load can be finished successfully, but db2diag.log
reported a lot of error message saying "Row hash mismatch"

ln -s 1.ixf 1.ixf.001
...
ln -s 1.ixf 1.ixf.008

db2 load from 1.ixf of ixf insert into XX partitioned db config
mode load_only_verify_part part_file_location

For a situation where a row is found on a wrong node is
acceptable in case when LOAD is asked to discard such rows, such
diagnose message should not be printed.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* V11.5 who use similar load scenario                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* ask for SB or wait for next release                          *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* V11.5 who use similar load scenario                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* ask for SB or wait for next release                          *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.07.2021
02.11.2021
02.11.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)