DB2 FOR LUW / DB2FORLUW / A10 - DB2

During SWAP operation, all the objects created by 
ADMIN_MOVE_TABLE during startup, will be cleaned. We can end up 
in a situation, where the drop UDI trigger operations on the 
source table are rolled back due to a -911 RC 68 SQL error. All 
the other objects like staging table are removed successfully, 
which leaves the UDI triggers in state inoperative on the new 
target table. The SQL911 error is never reported back to the end 
user, thus the SWAP operation finishes with success.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************

Manually drop the ADMIN_MOVE_TABLE UDI triggers from the target 
table after the SWAP operation finished successfully.

First fixed in DB2 Version 10.1 Fix Pack 5.

not known / see Local fix

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

11.07.2014
17.07.2015
17.07.2015