RELEASE NOTES FOR

IBM Informix ODBC Driver

Date: 07/19/2002

Version: 3.34 & 3.80


Table of Contents

I. Overview of Release Notes
II. Database Server Names and Versions
III. New Attributes
IV. XA Support
V. Unicode Support
VI. Fixed Problems
 


I. Overview of Release Notes

The purpose of this release notes document is to make you aware of any special
action required to configure and use the IBM Informix ODBC Driver on your
computer. This file also contains information about known bugs and their
workarounds.

This release notes document is not intended to be all-inclusive; it should
be used as an addendum to the Informix ODBC Driver manual, which provides
thorough information about product features and behavior.

This release will support 2 ODBC drivers 3.34 and 3.80, the latter is
Unicode enabled. The future releases of CSDK will have only one ODBC driver with both the capabilities.  

These release notes are written for the following audience:

+ System administrators who install Informix database servers
+ Database administrators who control access to IBM Informix databases
+ Developers who write applications using ODBC

Versions 3.34 & 3.80 of IBM Informix ODBC Driver have been tested with the following
database server configurations:

+ IBM Informix Dynamic Server, Version 5.10
+ IBM Informix Dynamic Server, Versions 7.24 and 7.3x
+ IBM Informix Dynamic Server with Advanced Decision Support and Extended
Parallel Options, Version 8.21 and Extended Parallel Server, Version
8.3x
+ IBM Informix Dynamic Server with Universal Data Option, Version 9.14
(Windows NT) and IBM Informix Dynamic Server 2000, Version 9.2x (UNIX)


II. Database Server Names and Versions

This document might not reflect the latest names of IBM Informix database
servers. The following table lists the database server versions and their
corresponding names.
 

Database Server Version Database Server Names
Numbers
5.x IBM INFORMIX-OnLine and IBM INFORMIX-SE
7.1x, 7.2x IBM INFORMIX-OnLine Dynamic Server and IBM INFORMIX-SE
7.3x IBM Informix Dynamic Server
8.1x IBM INFORMIX-OnLine XPS
8.2x IBM Informix Dynamic Server with Advanced Decision
Support and Extended Parallel Options
8.3 IBM Informix Extended Parallel Server (XPS) or
IBM Informix Enterprise Decision Server
9.01, 9.1 through 9.13 IBM INFORMIX-Universal Server
9.14 IBM Informix Dynamic Server with Universal Data
Option
9.2 IBM Informix Dynamic Server 2000


III. New Features

ODBC Driver 3.34 & 3.80
Support for XA
ODBC Driver 3.80
Support for Unicode


IV. XA Support (on 3.34 and 3.80 driver)

This section describes the new XA API with this release of the IBM Informix
ODBC Driver.

/* Function for acquiring the xa_switch structure
* defined by Informix RM
*/

struct xa_switch_t * _fninfx_xa_switch( void );
 

/* Function for obtaining the Environment
* handle associated with an XA Connection
*/

RETCODE IFMX_SQLGetXaHenv(int, HENV *);
 

/* Function for obtaining the Database handle
* associated with an XA Connection
*/

RETCODE IFMX_SQLGetXaHdbc(int, HDBC *);

#endif /* __INFXCLI_H */
 


V. Unicode Support on ODBC 3.80 driver (only)
 

An ODBC application may make calls to Unicode enabled ODBC APIs and/or ANSI ODBC APIs. For Unicode enabled APIs the application must link to Unicode enabled driver only whereas for ANSI ODBC APIs the application can link either to Unicode enabled driver or ANSI driver.

Compiling and running Unicode enabled ODBC applications on Unix:

A Unicode enabled application must set compile time as well as runtime flag to indicate the flavor of Unicode used. The compile time flags are -DUTF8, -DUCS2 and -DUCS4; the default being -DUCS4. The runtime Unicode flavor must be indicated in the [ODBC] section of odbc.ini file.

For eg:

     [ODBC]

     UNICODE=UCS-4

The supported values are UCS-2, UTF-8 and UCS-4; default being UTF-8.

Please note that the compile time default is UCS4 while runtime time default is UTF-8.

Applications linking to Merant Driver Manager & using Unicode enabled ODBC driver, should set Unicode flavor to UTF-8.



 

VI. Fixed Problems
 

Bug Number 

Description

129096

USING FULLY-QUALIFIED HOST NAME IN ODBC DRIVER SETUP CORRUPTS REGISTRY

133605

THE ESCAPE SEQUENCE FOR TIMESTAMP IS NOT INTERPRETTED IF THERE IS NO SPACE BETWEEN THE TS AND THE FIRST QUOTE

134342

USING THE CONCAT SCALAR FUNCTION WITH A CASE EXPRESSION AS ONE OF THE ARGUMENTS GENERATES A SYNTAX ERROR IN THE ODBC DRIVER 

134886

RUNNING A SELECT STATEMENT USING ODBC 3.32 (AND 3.32) CAUSES AN ERROR -363. THIS PROBLEM IS BASED ON THE PROBLEM 128336

135350

ERROR "ROWID DOES NOT EXIST" (-857) OCCURRED WHEN A QUERY AGAINST A FRAGMENTED TABLE IN MICROSOFT MSQUERY

144195

GET NONSENSE ERROR OF INCORRECT PARSING OF UPDATE STATEMENT WITH "INLINE" TEXT BLOB THROUGH ODBC

144636

A DSN-LESS CONNECTION PRODUCES A 'ARITHMETIC EXCEPTION (CORE DUMPED)' OR DIVIDE BY ZERO ERROR ON SUN

145011

NEW ODBC DRIVER GIVES SYNTAX ERROR FOR SQL

145167

 IF ACCESS 2000 IS USED TO LINK A TABLE USING ODBC 3.32 AN INTERVAL DATA TYPE IN THE LINKED TABLE IS DISPLYED AS GARBAGE

145267

ERROR -395 WHEN TRYING TO EXECUTE MULTIPLE OUTER JOINS USING ODBC SYNTAX. WORKS FINE WHEN THE NATIVE INFORMIX SQL SYNTAX IS USED

145463

ODBC DRIVER SEGV WHEN INSERTING A TEXT VALUE THAT CONTAINS A COMMA CHARACTER (',') 

146334 

WHEN CREATING A DSN, IF INCORRECT INFORMATION IS ENTERED THE ERROR MESSAGE REPORTED IS "UNSPECIFIED SYSTEM ERROR"

146592

THE VALUE FOR "VMB CHARACTER" IN THE ENVIRONMENT TAB OF THE DATA SOURCE ADMINISTRATOR IS GETTING CHANGED FROM  ESTIMATE TO EXACT WIHTOUT USER ACTION

147062

MEMORY LEAK IN ODBC 3.33 AND 3.80 BETA WHEN CALLING TO SQLEXECDIRECT() 

147282

SQLDESCRIBECOL FAILS TO REPORT CORRECT NULLABILITY OF OF UNDERLYING COLUMN DUE TO FIX FOR BUG 117497

147284

MTS TRANSACTIONS HUNG AND LEFT SOME OF THE CONNECTIONS HANGING FOREVER ON THE SERVER SIDE 

147307

SQLDRIVERCONNECT RETURNS UNSPECIFIED SYSTEM ERROR WHEN CONNECTION IS LOST

149522

ERROR -617 RETURNED IN SOME CONDITIONS INSERTING A TEXT VIA ODBC EVEN IN PATCH CSDK 2.60.TC2X4 THAT FIXES BUG # 145463

149962

INSERT VIA ODBC OF 2 ADJACENT STRINGS (2ND ONE BEING A TEXT) RETURNS ERROR -236 WITH CSDK 2.60.TC2X7 OR –617 WITH ANOTHER CSDK VERSION

149804

USING A COM OBJECT IF A DSNLESS CONNECTION HANGS CONNECTING TO SERVER 'A'. A 2ND DSNLESS CONNECTION WILL HANG CONNECTION TO SERVER 'B'.

150663

MTS TRANSACTION ENLISTMENT FAILS WITH MICROSOFT EFAIL MESSAGE GENERAL ERROR

151900

-25556 ERROR WHEN CONNECTING WITH THE SQLCONN32.EXE USING THE 3.80 ODBC DRIVER

153549

ODBC 3.80: A SYNTAX ERROR, INSERTING A JAPANESE MULTI-BYTE CHARACTER

150327

SQLCOLUMNS FAILS WITH ERROR -201, WHEN TRIED TO FETCH DETAILS OF A SYNONYM WHICH IS CREATED FOR A TABLE IN DIFFERENT DATABASE

151464

WITH DELIMIDENT=Y THE ODBC DRIVER GENERATES A 11060 GENERAL ERROR USING IDENTIFIERS THAT CONTAIN A SPACE WHEN EXECUTING CERTAIN SQL STATEMENTS

154575

GET GENERAL ERROR OR CATASROPHIC FAILURE TRYING TO INSERT TEXT INTO TEXT BLOB

154955

LITERAL STRING LONGER THEN 256 CHARACTERS AND CONTAINING 2 CONSECUTIVE SINGLE QUOTES RETURNS ERROR -280 IN INSERT WITH SQLEXECDIRECT

155267

MSQUERY CORE DUMP ON A ANSI DATABASE WITH SYNONYMS WHEN  SELECTING TABLE WITHIN MS QUERY ASSISTENT (3.34 DRIVER)

155405

USING ODBC HAVING A TRIM FUNCTION PLACED IN A WHERE CLAUSE OTHER THAN THE FIRST CONDITION GENERATES A GENERAL SYNTAX ERROR

155884

USING ODBC XA: IF A ROLLBACK OCCURS THE NEXT ODBC CALL TO XASTART WILL RETURN A 1 AND NEVER SEND A SQ_XSTART TO THE ENGINE

155910

INSERTING A BLANK STRING INTO A TEXT COLUMN GIVES ERROR

156689

MORE THAN 33 PARAMETERS TO A STORED PROCEDURE GIVES INCORRECT SCHEMA FOR DIAGNOSTICS IN ODBC


 

Copyright (c) 2002, IBM Corporation, All rights reserved