DB2 FOR LUW / DB2FORLUW / A50 - DB2

With DB2 10.5 FP5 and later when running a LOAD in a DPF
environment on a table with constraints, a deadlock can occur on
the SYSTABLES table.
This occurs due to the multiple nodes trying to run a SET
INTEGRITY OFF command, which is run automatically as part of the
LOAD, at the same time and getting a lock conflict on the row
for this table in the SYSTABLES table.

This only occurs when running a concurrent LOADs on the same
table on multiple partitions. This will not occur is running
multiple LOADs on different tables.

****************************************************************
* USERS AFFECTED:                                              *
* All DB2 DPF users                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Customer should use local fix: Run SET INTEGRITY OFF prior   *
* to running the LOAD command.                                 *
****************************************************************

Run SET INTEGRITY OFF prior to running the LOAD command.

not known / see Local fix

forerunner  : 
follow-up : IT24764 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.06.2016
07.01.2020
07.01.2020