home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT02978 Status: Closed

ADMIN_MOVE_TABLE MAY FAIL TO DROP UDI TRIGGERS FROM SOURCE TABLE DURING
SWAP OPERATION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 10.                      * 
****************************************************************
Local Fix:
Manually drop the ADMIN_MOVE_TABLE UDI triggers from the target 
table after the SWAP operation finished successfully.
Solution
First fixed in DB2 Version 9.7 Fix Pack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.07.2014
09.12.2014
09.12.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList