DB2 - Problembeschreibung
Problem IC76119 | Status: Geschlossen |
CREATE INDEX MAY GET SQL0901N IF COLUMN HAS INVALID UTF8 CHARACTERS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
If the column on which index is created has invalid UTF characters, reate index statement may get SQL0901N with reason "Key data mismatch encountered during key delete". Simple repro: #!/bin/ksh export DB2OPTIONS="-ctv" dbName="xxxxxx" db2start db2 "create db $dbName collate using SYSTEM_819_US" db2 "connect to $dbName" db2 "create table t1 (v1 varchar(3), i2 int)" db2 "insert into t1 values (x'45C3A8',1), (x'4599EB',2)" db2 "create index i1 on t1 (v1)" SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "Key data mismatch encountered during key delete".) SQLSTATE=58004 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * Create index may report sql901 if index is created on * * invalid UTF-8 characters. * * * * SQL0901N The SQL statement failed because of a non-severe * * system error. * * Subsequent SQL statements can be processed. (Reason "Key * * data mismatch * * encountered during key delete".) SQLSTATE=58004 * **************************************************************** * RECOMMENDATION: * * Upgrade the product. * **************************************************************** | |
Local-Fix: | |
DB2SET DB2_BINSORT=NO; and recreate the indexes in { {13;21}, {10;23}, {10;35}, {13;14}, {13;30}, {16;12} } | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC76121 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 02.05.2011 05.07.2011 05.07.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
9.5.0.8 |