DB2 FOR LUW / DB2FORLUW / A50 - DB2

When running db2move in 2 step mode (DDL_ONLY & LOAD_ONLY), not
all integrity conditions are reactivated when foreign key
constrains exist.
After the LOAD_ONLY step some objects may remain in
CHECK-PENDING state, so that it is necessary to do a
manual 'SET INTEGRITY FOR ... IMMEDIATE CHECKED' to make the
tables available again.

Logfile COPYSCHEMA.err contains:
SQL3608N Cannot check a dependent table ".

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Use the local workarounds or update to Db2 version 11.1 once *
* APAR IT27946 is closed.                                      *
****************************************************************

Do one of the following:
- provide the list of tables (with -tn or -tf option) in an
order to specify parent tables before child tables or
- manually run 'SET INTEGRITY FOR ... IMMEDIATE CHECKED' for the
tables being left in Set Integrity Pending state or
- use the one step mode DDL_AND_LOAD

not known / see Local fix

forerunner  : 
follow-up : IT27946 

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

28.01.2019
13.03.2020
13.03.2020