home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC68425 Status: Closed

INFORMIX WRAPPER RETURNS SQL1822N ERROR WHEN USING RTRIM FUNCTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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
available fix packs:
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

Solution
First Fixed in DB2 V9.7 FixPack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.05.2010
12.03.2012
12.03.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList