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

INCORRECT RESULTS POSSIBLE IN CASES WHERE A COLUMN ORGANIZED TABLE IS
MODIFIED BY TWO TRANSACTIONS AT THE SAME TIME

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In cases where multiple update or delete statements are 
occurring on a given column-organized table at the same time, 
one or more of the statements may not act on the correct set of 
rows.  For example, if the following two statements are ran at 
the same time in different transactions: 
 
update t1 set c1 = 5 where c1 = 4; 
delete from t1 where c1 = 5 or c1 = 4; 
 
and the transaction performing the update statement commits 
first, it is expected that the delete transaction will leave the 
table without any rows where c1 = 5 or c1 = 4.  In some 
circumstances, however, the table will be left with one or more 
rows where c1 = 5 or c1 = 4. 
 
Note that this issue ONLY affects tables which were populated 
using an insert-subselect statement on releases 10.5, 10.5 FP1, 
10.5 FP2, or 10.5 FP3.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of column-organized tables                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************
Local-Fix:
Populate tables using either LOAD, INGEST, or an insert-values 
statement.  Alternatively, do not run concurrent updates or 
delete statements against the column-organized tables in your 
database which were populated using insert-subselect.
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in DB2 UDB version 10.5 fix pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.08.2014
08.09.2014
09.04.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList