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

DELETE NOT REMOVING DATA FROM MDC TABLE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The problem occurs while running a delete on an MDC table that 
contains overflow records such that the pointer record being 
deleted is not the last record in the block, but the overflow 
record pointed to by that pointer record is the last record of a 
different block. 
 
Steps to reproduce this problem: 
#!/bin/ksh 
 
dbName="wsdb" 
export DB2OPTIONS="-ctv" 
 
db2start 
db2 "create db $dbName" 
db2 "connect to $dbName" 
db2 "create tablespace ts1 extentsize 2" 
db2 "create table t1 (i1 int, i2 int, c3 char(250), c4 
char(250), c5 char(250), 
v6 varchar(250)) organize by (i1) in ts1" 
 
dataFile="data.del" 
rm -f $dataFile 
typeset -i i=0 
while [ $i -lt 10 ] 
do 
  echo "0,$i,$i,$i,$i,$i" >> $dataFile 
  i=$i+1 
done 
 
db2 "import from $dataFile of del insert into t1" 
rm -f $dataFile 
db2 "update t1 set 
v6='012345678901234567890123456789012345678901234567890123456789 
0123456789012345678901234567890123456789012345678901234567890123 
4567890123456789012345678901234567890123456789012345678901234567 
890123456789' 
where i2=0" 
db2 "delete from t1 where i2 >= 0" 
db2 "select count(*) from t1 where i2 >= 0" 
db2 "drop table t1" 
db2 "drop tablespace ts1" 
db2 "terminate" 
db2stop 
 
There is no workaround for this problem. 
 
Note: this problem does NOT exist in 9.5 and earlier releases.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 fix pack 2.                   * 
****************************************************************
Local-Fix:
There is no workaround for this problem.
verfügbare FixPacks:
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
The problem was first fixed in DB2 UDB Version 9.7 fix pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66836 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.02.2010
30.06.2010
30.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList