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 IC63122 Status: Geschlossen

ADMIN_MOVE_TABLE DATA LOSS DUE TO TRIGGERS NOT FIRING FOR CURREN TLY
EXECUTING OR PREPARED STATEMENTS AGAINST THE SOURCE TABLE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In ADMIN_MOVE_TABLE during the INIT phase, a number of triggers 
are created on the source table to capture any data changes. In 
v97, CREATE TRIGGER uses soft invalidation instead of hard 
invalidation. This means that any currently executing or 
prepared statements against the source table can execute without 
firing the triggers, with the end result being data loss during 
the REPLAY phase.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of ADMIN_MOVE_TABLE                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In ADMIN_MOVE_TABLE during the INIT phase, a number of       * 
* triggers are created on the source table to capture any data * 
* changes. In v97, CREATE TRIGGER uses soft invalidation       * 
* instead of hard invalidation. This means that any currently  * 
* executing or prepared statements against the source table    * 
* can execute without firing the triggers, with the end result * 
* being data loss during the REPLAY phase.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to FP1 for v97 to get the fix.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
At the end of the INIT phase drive a hard invalidation of all 
currently executing or prepared statements against the table. By 
doing this those changes will be picked up by the triggers, 
eliminating the data loss. Upgrade to FP1 for v97 to get the 
fix.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.09.2009
16.02.2010
16.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.1 FixList