home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT03099 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Manually drop the ADMIN_MOVE_TABLE UDI triggers from the target 
table after the SWAP operation finished successfully.
Lösung
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.07.2014
17.07.2015
17.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList