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

INFORMIX WRAPPER RETURNS SQL1822N ERROR WHEN USING RTRIM FUNCTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
You will receive an  SQL1822N error if you meet both of the 
following condition: 
(1)Using rtrim function in  Informix server version 11 
(2)the column to be trimed contains null value 
 
This problem occurs since v91 fixpack9, in which the error 
reported is 
like below: 
SQL1822N  Unexpected error code "-201 (offset 68)" received from 
data source 
   "DATASTORE2". Associated text and tokens are "A syntax error 
has occurred.". 
   SQLSTATE=560BD 
 
 
For example: 
 
create wrapper informix; 
create server DATASTORE2 type informix version 11.0 wrapper 
informix.........; 
create user mapping for user server DATASTORE2............; 
set passthru DATASTORE2; 
create table testtbl (ch char(10)); 
insert into testtbl values('aaa'); 
insert into testtbl values(null); 
set passthru reset; 
create nickname "nick1" for "DATASTORE2"."j15user1"."testtbl"; 
db2 => select ch from "nick1" where rtrim(ch) = 'a' 
 
CH 
---------- 
SQL1822N  Unexpected error code "-201 (offset 68)" received from 
data source 
"DATASTORE2". Associated text and tokens are "A syntax error has 
occurred.". 
SQLSTATE=560BD
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description Above                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to FixPack 3 or higher.                              * 
****************************************************************
Local-Fix:
change the Informix server version from 11 to 10
verfügbare FixPacks:
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 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
First Fixed in DB2 V9.7 FixPack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.05.2010
12.03.2012
12.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList