|
Problem IC63552
|
Status: Geschlossen |
SQL1034C CAUSED BY UPDATE OF A MULTIDIMENSIONAL CLUSTERED KEY IN A DATABASE WITH A LOCALE-SENSITIVE UCA-BASED COLLATION |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
SQL1034C may result when all of the following criteria are
satisfied:
(1) The database is defined with a locale-sensitive UCA-based
collation.
(2) The table is a multidimensional clustered (MDC) table.
(3) The MDC key column is being updated from value1 to value2,
where the two values collate as equal but are not identical when
compared byte-for-byte.
(4) The MDC key column being updated is of short string type
(i.e. char, varchar, graphic, or vargraphic).
.
Example:
.
create db wsdb using codeset UTF-8 territory US collate using
UCA500R1_LROOT_AN_CX_EX_FX_HX_NO_S1;
connect to wsdb;
.
create table tab1 (vc1 varchar(1) )organize by (vc1);
insert into tab1 values ('B');
update tab1 set vc1='b' where vc1='B';
.
-- SQL1034C results
delete from tab1 where vc1='B';
. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Customers with multidimensional clustered tables in a *
* database defined with local-sensitive UCA-based collation. *
****************************************************************
* PROBLEM DESCRIPTION: *
* SQL1034C may result when all of the following criteria are *
* satisfied: *
* (1) the database is defined with a locale-sensitive *
* UCA-based collation *
* (2) the table is a multidimensional clustered (MDC) table *
* (3) the MDC key column is being updated from value1 to *
* value2, where the two values collate as equal but are not *
* identical when compared byte-for-byte. *
* (4) the MDC key column being updated is of short string type *
* (i.e. char, varchar, graphic, or vargraphic) *
* *
* Example: *
* *
* create db wsdb using codeset UTF-8 territory US collate *
* using UCA500R1_LROOT_AN_CX_EX_FX_HX_NO_S1; *
* connect to wsdb; *
* *
* create table tab1 (vc1 varchar(1) )organize by (vc1); *
* insert into tab1 values ('B'); *
* update tab1 set vc1='b' where vc1='B'; *
* *
* -- SQL1034C results *
* delete from tab1 where vc1='B'; *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 Fix Pack 1 or above. *
**************************************************************** |
| Local-Fix: |
Avoid any one of the criteria mentioned in the Description
section, |
| 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 |
Problem first fixed in DB2 version 9.7 Fix Pack 1. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 02.10.2009
24.02.2010
24.02.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP1
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.1
|
 |
