DB2 - Problem description
Problem IC67248 | Status: Closed |
SQLExecute in CLI returns SQL401N for comparison operators when using deferred prepare against a non-unicode target database | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
SQL401N is returned when all of the following conditions are satisfied: (1) Registry variable DB2_DEFERRED_PREPARE_SEMANTICS=YES or DB2_COMPATIBILITY_VECTOR=ORA has been set (2) target database is a non-unicode database (3) SQLExecute in CLI is preparing a statement with a comparison operator (4) One operand of the comparison operator mentioned in (3) is a parameter marker and C type/data used is double byte. (5) The other operand of the comparison operator in (3) resolves to type CHAR or VARCHAR | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.8 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.8 FixPack 3. * **************************************************************** | |
Local Fix: | |
(1) Issue "db2set DB2_DEFERRED_PREPARE_SEMANTICS=NO", or (2) Use single byte data instead of double byte data in the application. For example, if you are using UCS-2 data and SQL_C_WCHAR C_Type, switch to using Unicode 1208 codepage and data, and SQL_C_CHAR C_Type in the application. | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.8 FixPack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.03.2010 23.12.2010 23.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.3 |