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

CLPPLUS RETURNS "DB250000I: THE COMMAND COMPLETED SUCCESSFULLY"
UNEXPECTEDLY WHEN CREATE AN ALREADY EXISTING SAME NAME INDEX

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
CLPPlus returns "DB250000I: The command completed successfully." 
message unexpectedly when create an already existing same name 
index. 
 
Problem Reproducible Steps: 
---------------- 
$ db2 create db sample 
$ db2 connect to sample 
$ more repro.sql 
set echo on 
create table t1 (c1 int); 
create index i1 on t1(c1); 
create index i1 on t1(c1); 
exit 
$ db2 drop table t1 
DB20000I  The SQL command completed successfully. 
$ clpplus -nw -s db2inst1/db2inst1@myserver:myport/sample @repro 
 
DB250000I: The command completed successfully. 
 
 
DB250000I: The command completed successfully. 
 
 
DB250000I: The command completed successfully. 
---------------- 
* Last DB250000I is not expected since the index i1 was created 
already in the above steps. 
 
If we do the same steps from CLP, it returns SQL0605W as below 
as expected. 
---------------- 
$ more repro_clp.sql 
create table t1 (c1 int); 
create index i1 on t1(c1); 
create index i1 on t1(c1); 
 
$ db2 -tvf repro_clp.sql 
create table t1 (c1 int) 
DB20000I  The SQL command completed successfully. 
 
create index i1 on t1(c1) 
DB20000I  The SQL command completed successfully. 
 
create index i1 on t1(c1) 
SQL0605W  The index was not created because an index 
"DB2INST1.I1" with a 
matching definition already exists.  SQLSTATE=01550 
----------------
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 5.                            * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.7 FixPack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.06.2011
16.12.2011
16.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList