I. Customer-reported bugs fixed
in CSDK 2.80 release
ESQL/C
95289 | -369 ERROR WHEN RUNNING ESQL PROGRAM COMPILED WITH ESQL 7.24.UC1 AGAINST I-CONNECT 2.01 AND 7.30.UC3 IDS ENGINE |
95317 | 7.2 ESQL OBJECTS DON'T RUN WITH 7.3 ENGINES ON AIX - GET ERRORS ABOUT MISSING LIBRARIES |
117791 | ESQL/C PROGRAM CORE DUMP WITH CLIENT_LOCALE "JA_JP.SJIS" |
120626 | ESQL PREPROCESSOR BLANKS OUT COLUMN NAME IF COLUMN NAME IS "COLLECTION" OTHER RESERVED WORDS USED AS COLUMN NAMES COMPILE FINE. |
121743 | AN ESQL/C PROGRAM THAT ALSO CONNECTS TO A DATABASE THROUGH ODBC WILL SEGV UPON EXITING. |
126689 | XA_OPEN() CANNOT ESTABLISH MORE THAN ONE CONNECTION AT A TIME IN A MULTI-THREADED ENVIRONMENT ON WINDOWS NT |
128965 | UPGRADING FROM ESQL/C 7.2X TO SDK 2.40 WITHOUT RECOMPILATION RESULTS IN UNDEFINED SYMBOLS ISNAN() AND FINITE() UPON APPLICATION EXEC |
131269 | GET ERROR WHEN COMPILING ESQL/C 9.30.HC1 WHEN USING -AC SWITCH (ANSI OFF) |
132391 | SQLI CODE DOES NOT SUPPORT 8.31 SERVER FOR XA CODE |
132428 | FE CLIENT DOES INFINITE LOOP IN _IWRITE FUNCTION WHEN REMOTE ENGINE IS SHUTDOWN AND THEN CLIENT ESQLC PROGRAM ISSUES AN EXECUTE DOING BLOB INSERT |
133399 | ERROR 'MEMORY CAN NOT BE READABLE', IF NO MI_ FUNCTION IS USED |
133682 | IN ESQL VERSION 9.30.UC1 THAT COMES WITH SDK 2.40, IF YOU DO NOT LEAVE A SPACE AFTER A LINE BEFORE A COMMENT, IT GIVES A SYNTAX ERROR. |
134808 | FUNCTION NAME LOST AFTER PREPROCESSING WHEN NO SPACE BETWEEN THE OPENING CURLY BRACE ('{') AND THE FUNCTION CALL AND ARGUMENT IS AN SQL |
135418 | ENABLING AND THEN DISABLING DEFERRED PREPARE WITH OPTOFC SET WILL RESULT IN A 361 ERROR |
144326 | RSETNULL(SQLDATE,PTR) USES AN 8BYTE VALUE FOR INTNULL BUT DATE DATA TYPE IS ONLY 4 BYTES WHICH RESULTS IN BUS ERROR ON 64 BIT PLATFORMS |
147567 | USING COMPOSITE (STRUCT) HOST VARIABLE WITH SET DESCRIPTOR, ESQL/C GIVES PREPROCESSOR ERROR -33006, TYPE IS NOT APPROPRIATE FOR THIS |
148165 | SEGMENTATION FAULT CORE DUMP OR WRONG ROWS RETURNED WITH PROGRAM WHICH PERFORMS ABSOLUTE FETCH ON A TABLE WITH VARIABLE LENGTH DATA (VARCHAR) |
149277 | PREPROCESSING ESQL/C, SYNTAX ERROR WHEN SEMICOLONS REMOVED FROM PARAMETERS AFTER USING LITERAL INTERVAL IN PRIOR FUNCTION |
149743 | COMPILING THE ESQL DEMO3 APPLICATION USING -THREAD OPTION CAUSES MEMORY LEAK |
150359 | EVEN THOUGH LENGTH OF THE CURSOR NAME IS <18 CHAR, GETTING ERROR -200 WHEN OPENING THE CURSOR WHEN THE PROG. IS COMPILED WITH "-LOCAL" OPTION |
150364 | IF TABLE HAS VARCHAR COLUMN, DBLOAD DISPLAYED INCORRECT ERROR MESSAGE |
150910 | DECLARING AN ARRAY OF DATETIME GIVES LONG C-CODE |
150923 | USING COMPOSITE (STRUCT) HOST VARIABLE WITH GET DESCRIPTOR AND EXECUTE USING DESCRIPTOR, ESQL/C PREPROCESSOR PRODUCES ERROR -33006. |
151374 | MEMORY LEAK CAUSING -406 ON XA CLIENT (TUXEDO SERVICE) RUNNING TX IN A LOOP |
151375 | ERROR -258 IN XA ENVIRONMENT AFTER WE EXECUTE A STATEMENT IN A TMJOIN'ED TX. CLIENT WILL SEND -1 SQLID TO THE SERVER. |
151673 | ATTEMPTING TO OPEN 1000 THREADS WITH ESQLC APPLICATION CAUSES A CORE DUMP |
152185 | SYNTAX ERROR -33051 OCCURS AT INVALID OR NON-EXISTENT LINE NUMBER WHEN USING EXEC SQL INCLUDE OR $INCLUDE INSIDE A DECLARE SECTION BLOCK |
152580 | ESQL/C CLIENT HANGS (CRASHES FOR CUSTOMER) IF THE CLIENT EXECUTES A UDR THAT RAISES AN ERROR WITH A MESSAGE LENGTH > 32K. |
152991 | INSERT INTO COLLECTION LIST CONTAINING VARCHAR FAILS WHEN USING COLLECTION HOST VARIABLE |
153225 | CORE DUMP WHEN ACCESSING LVARCHAR IN DESCRIPTOR AFTER IFX_VAR_DEALLOC |
153555 | UNALIGNED ACCESS ERROR WHEN USING XA LIBRARIES IN SIMPLE ESQL/C CODE ON DEC WITH SDK 2.50.FC1 |
153659 | UNDEFINED SYMBOL _IQFREMOVEALL WHEN ESQL -STATIC -THREAD (THREADLIB=SOL) ON DEMO1.EC |
154539 | WHEN ACCESSING OPTICAL BLOB DESCRIPTOR WITH USER ALLOCATED MEMORY LOC_T.LOC_BUFSIZE REQUIRED TO BE SIZE OF BLOB INSTEAD OF DESCRIPTOR (112) |
154948 | ESQL/C CANNOT INTERPRET VARIALBLE WITH RESERVE WORD 'FROM' IN A SELECT - INTO - |
155189 | ON HP GETLOGIN_R RETURNS 0 ON SUCCESS AND ERROR ON FAILURE. THIS CHECK IS INCORRECT IN OSFUTIL.C |
ODBC
108697 | ODBC DRIVER FAILS TO POPULATE ROWCOUNT PROPERTY OF RDORESULTSET OBJECT IN VISUAL BASIC PROGRAM UNLESS MOVELAST METHOD IS EXPLICITLY EXECUTED |
108775 | ODBC CLI ON NT DOES NOT GIVE THE CORRECT ROW FOUND TO VB RDO OPENRESULTSET ROWCOUNT |
110640 | UNICODE CLIENT GETS TRUNCATED DATA FROM 8859-1 DATABASE ON USING FETCH ARRAYS |
111304 | USING ODBC 3.30 DRIVER AGAINST A METACUBE DSS SYSTEM WHICH CONTAINS SYNONYMS, COLUMNS FROM SYNONYM TABLES ARE NOT VISIBLE IN WAREHOUSE |
111505 | QUERYING DATES FROM A TABLE WITH A COLUMN DEFINED AS DATETIME YEAR TO MONTH RETURNS INCORRECT RESULTS |
114054 | WHEN USING MSACCESS OR VB TO ACCESS A UDO DATABASE (WITH UDTS) USING ODBC 3.3 DRIVER, ERROR 11013 IS REPORTED. |
115016 | ADO RETURNS #ERROR WHEN RETRIEVING DATETIME HOUR TO MINUTE. |
116296 | MS-ACCESS CAN'T LINK TO CLOB/BLOB TABLE, ERROR -11092 IN TRACE |
116726 | SQLGETDATA PUTS THE WRONG VALUE IN THE LENGTH OR INDICATOR POINTER WHEN SELECTING AN INTERVAL DAY TO HOUR INTO AN SQL_C_CHAR |
117497 | NO ROWS WILL BE RETURNED ON VB, IF THE QUERY IS AN OUTER JOIN AND ONE OF THE COLUMN CONTAINS NULL VALUES |
122039 | MALFUNCTION OF MULTIPLE CONNECTIONS USING ONE DSN IN VB DAO APPLICATION |
122918 | CANNOT LINK STATIC ODBC DRIVER INTO A SHARED LIBRARY |
124752 | USING ADUSECLIENT IN ADO APPLICATION CAUSES TRUNCATION WITH DECIMAL COLUMNS |
126214 | SCROLLABLE CURSORS FAIL TO HOLD LOCKS ON CERTAIN OPERATIONS WHICH INTERSOLV 3.11 DRIVER WOULD HOLD LOCK |
126817 | ODBC DRIVER FAILS TO ENLIST TRANSACTION WHEN USING DSNLESS CONNECTION WITH MTS |
127812 | LOOSELY COUPLED THREADS DO NOT SHARE THE SAME LOCK SPACE CAUSING DEADLOCKS USING MTS. - SAME BUG AS 111953 |
127885 | CATASTROPHIC FAILURE" WHEN REQUERY AFTER ADO BEGINTRANS COMMITTRANS IF PASSING CONNECTION STRING WITH NO DSN, WITH INFORMIX 3.31 |
128244 | SYNTAX ERROR TRYING TO EXECUTE A QUERY INVOLVING A COLLECTION DERIVED TABLE |
129027 | CANNOT INSERT MORE THAN 32K THROUGH A BOUND VARIABLE WITH AN SQL TYPE OF SQL_INFX_UDT_X: ERROR -11023: RIGHT STRING TRUNCATION |
129096 | USING FULLY-QUALIFIED HOST NAME IN ODBC DRIVER SETUP CORRUPTS REGISTRY |
130096 | SQLEXECDIRECT DUMPS CORE EXECUTING A SELECT STATEMET WITH A LONG IN CLAUSE AND ODBC TRACE IS ON USING DRIVER MANAGER REPLACEMENT MODULE |
130673 | MEMORY LEAK - SQLFREESTMT DOESN'T RELEASE MEMORY AFTER SQLCOLUMNS |
130975 | ODBC ARRAY INSERT DOESN'T CORRECTLY REPORT STATUS FOR INDIVIDUAL ROWS (DUPLICATE KEY REPORTED FOR WRONG ROW) |
130979 | ODBC PROGRAMS WITH OPTOFC ENABLED DUMP CORE WHEN HOST VARIABLES ARE USED |
133022 | MTS HANGS IN A PREPARING STATE RUNNING SERVERAL MULTI-THREADED COMPONENTS |
133605 | THE ESCAPE SEQUENCE FOR TIMESTAMP IS NOT INTERPRETED 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 |
134705 | ODBC DRIVER REPORTS TO ADO THAT ADBOOKMARK FUNCTIONALITY IS NOT SUPPORTED WHEN USING SERVER SIDE CURSORS, WORKS WITH CLIENT SIDE CURSOR |
135335 | -9634 ERROR USING ADO.UPDATE AND LVARCHAR DATATYPES |
144195 | GET ERROR OF INCORRECT PARSING OF UPDATE STATEMENT WITH "INLINE" TEXT BLOB THROUGH ODBC |
145011 | NEW ODBC DRIVER GIVES SYNTAX ERROR FOR SQL |
145267 | ERROR -395 WHEN TRYING TO EXECUTE MULTIPLE OUTER JOINS USING ODBC SYNTAX. WORKS FINE WHEN THE NATIVE INFORMIX SQL SYNTAX IS USED. |
147307 | SQLDRIVERCONNECT RETURNS UNSPECIFIED SYSTEM ERROR WHEN CONNECTION IS LOST |
147377 | -266 NO CURRENT ROW FOR UPDATE/DELETE CURSOR AFTER COMMIT AND FETCH IN ODBC AND WITH CURSORBEHAVIOR SET TO PRESERVE |
147769 | ODBC 3.33 DOES NOT FORMAT THE DECIMAL VALUE WHEN USING SPANISH LOCALE IN WINDOWS REGIONAL SETTINGS. |
149119 | CPP APPLICATION CORE DUMPS WITH ODBC 3.33 DRIVER ON 'SELECT * FROM 'INFORMIX'.SYSTABLES' |
149415 | CREATING FILE DSN ON WINDOWS DOES NOT SAVE LOCALES INFORMATION |
149522 | ERROR -617 RETURNED IN SOME CONDITIONS INSERTING A TEXT VIA ODBC EVEN IN PATCH CSDK 2.60.TC2X4 THAT FIXES BUG # 145463 |
149804 | USING A COM OBJECT IF A DSNLESS CONNECTION HANGS CONNECTING TO SERVER 'A'. A 2ND DSNLESS CONNECTION WILL HANG CONNECTION TO SERVER 'B'. |
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 |
150327 | SQLCOLUMNS FAILS WITH ERROR -201, WHEN TRIED TO FETCH DETAILS OF A SYNONYM WHICH IS CREATED FOR A TABLE IN DIFFERENT DATABASE |
150484 | THROUGH ODBC DRIVER SELECT STAMENT WITH IN CLAUSE ERRORS OUT WHEN SELECTING INTO A TEMP TABLE. |
150722 | MS ACCESS WITH INFORMIX ODBC 3.3X DOES NOT DISPLAY ALL THE DECIMAL ZEROS, USING INTERSOLV 3.11 (SDK 2.30) ALL DECIMAL ZEROS ARE DISPLAYED |
151464 | WITH DELIMIDENT=Y THE ODBC DRIVER GENERATES A 11060 GENERAL ERROR USING IDENTIFIERS THAT CONTAIN A SPACE WHEN EXECUTING CERTAIN SQL |
151900 | -25556 ERROR WHEN CONNECTING WITH THE SQLCONN32.EXE USING THE 3.80 ODBC DRIVER |
152303 | LOCKING ERRORS ARE NOT RETURNED TO ADO VIA ODBC AND OLEDB |
152507 | SQL_QUERY_TIMEOUT OPTION REQUIRED IN ODBC DRIVER |
153223 | CLI 3.34 OPENS ADDITIONAL SYSTEM CATALOG CALLED SYSFRAGMENTS THEREBY BREAKING COMPATIBILITY TO STANDARD ENGINE ( SE ) |
153549 | ODBC 3.80: A SYNTAX ERROR, INSERTING A JAPANESE MULTI-BYTE CHARACTER |
153589 | SQLSETPOS FUNCTION WITH SQL_UPDATE RETURNS MICROSOFT ODBC CURSOR LIBRARY ERROR 'CURSOR LIBRARY NOT CAPABLE' AND INFORMIX ERROR -11092 (ODBC3.34) |
153814 | CANNOT UPDATE/INSERT A LINKED TABLE IN MS ACCESS 2000 CONTAINIG A DECIMAL FIELD WHEN USING WITH DB_LOCALE/CLIENT_LOCALE=DE_DE.819 -ERROR |
154076 | ERROR -217,COLUMN COLUMN-NAME NOT FOUND IN ANY TABLE IN THE QUERY, USING MS ACCESS AND INFORMIX ODBC DRIVER TO IMPORT A DATABASE SYNONYM |
154575 | GET GENERAL ERROR OR CATASROPHIC FAILURE TRYING TO INSERT TEXT INTO TEXT BLOB |
154672 | UNABLE TO SELECT SERIAL COLUMN USING OLEDB PROVIDER WITH MS SQL SERVER 2000 LINK SERVER |
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) |
155737 | RUNNING A LARGE QUERY(ABOUT 15K) IN MS ACCESS PASS THROUGH QUERY, GIVES RESERVED ERROR ( -7711 ), THERE IS NO MESSAGE FOR THIS ERROR. |
155825 | INSERTING INTO A QUOTED TEXT STRING INTO A TEXT BLOB THROUGH ODBC HAS ERRONEOUS RESULTS. PRIOR COLUMNS BEING INSERTED OVERWRITES TEXT COLUMN. |
155826 | INSERTING A BLANK STRING INTO A CHAR COLUMN THAT PRECEDES A TEXT COLUMN GIVES A 236 ERROR IN SOME CASES. |
155858 | ODBC DOES NOT RETURN XA ERRORS |
156095 | ODBC RECIEVCES A -6 ON A XA_START() BECAUSE NO XA_OPEN WAS SENT |
156125 | CLIENT AND SERVER HANG WHEN USING MTS (ODBC) AGAINST 9.30 ENGINE |
OLEDB
117912 | THE OLEDB PROVIDER IS APPROXIMATELY 2 TIMES AS SLOW AS AS THE INFORMIX ODBC 3.30 DRIVER AND THE INTERSOLV 3.50 AND 3.11 DRIVERS |
128105 | ERROR 1218 - STRING TO DATE CONVERSION ERROR WHEN QUERYING WITH A WHERE CLAUSE ON A COLUMN DATE USING ANY FORMAT DIFFERENT THAN 4YMD/ |
130144 | VB 6.0 CRASHES WITH OLEDB 2.1 FOR SELECT OF MONEY COLUMN=0 |
132676 | MSDATASHAPE IN VB/ADO CAUSE OLEDB PROVIDER TO SEND A BOGUS UPDATE STATEMENT TO ENGINE AND LEAVE THE CONNECTION UNDISCONNECTED |
144767 | MEMORY LEAK CRASHES VISUAL BASIC WHEN USING PREPARED INSERT STATEMENT TO LOAD INTO A TEXT COLUMN |
145130 | MEMORY LEAK IN OLEDB DRIVER WHEN CONNECTING/DISCONNECTING |
145462 | ERROR -324 AMBIGUOUS COLUMN(ROWID) ON SELECT USING ADO RECORDSET WITH ADOPENKEYSET AND ADLOCKREADONLY |
145636 | MEMORY LEAK AT INSERTION OF BLOBS IN COLUMN OF TYPE BYTE |
150937 | NEED TO MAKE OLEDB NOT REQUIRE DELIMIDENT=Y TO WORK MICROSOFT PRODUCTS [SERVER] |
151379 | OLE-DB SCHEMA ROWSET OPERATIONS FAIL DUE TO TYPE INCOMPATIBILITY WHEN METADATA CONTAINS A BOOLEAN VALUE |
151638 | THE REGULAR INSTALL PROCESS OF SDK DOES NOT CORRECTLY REGISTER THE IFXOLEDBC.DLL FOR SQL SERVER TO USE |
151864 | INCONSISTENT METADATA ERROR MESSAG USING INFORMIX OLE/DB AND MS SQL SERVER 2000 LINK SERVER OPTION RUNNING A SELECT AGAINST NOT NULL CO |
152540 |
CANNOT INSERT INTO SMART BLOB COLUMN USING ADO APPENDCHUNK
METHOD |
153491 | "SELECT DISTINCT COLNAME" IS CHANGED TO "SELECT DISTINCT ROWID, COLNAME" WITH SERVER-SIDE CURSORS IN ADO AND OLEDB. |
153984 | OLEDB PROVIDER ALWAYS COMMITS WHEN IN MTS TRANSACTION EVEN IF SETABORT CALLED |
LIBC++
146763 | UNABLE TO DYNAMICALLY LOAD LIBIFDMR.SO IN CPP PROGRAM -8 EXEC FORMAT ERROR |
LIBDMI
111687 | MEM LEAK, THREAD OVERHEAD. |
135354 | USING MI_STRING_TO_INTERVAL IN CLIENT PROGRAM DOES NOT WORK, EXHIBITS DIFFERENT BEHAVIORS ON VARIOUS OS PLATFORMS |
144079 | MI_TYPE_TYPENAME DOES NOT RETURN QUALIFYING INFORMATION FOR DATETIME AND INTERVAL |
154360 | CANT SEND OPAQUE TYPES FROM THE CLIENT TO THE SERVER, YOU GET A -9628 |
INSTALL
96918 | INSTALLATION OF CLIENT SDK AFTER ESQL/COBOL RESULTS IN UNRESOLVED SYMBOLS |
101569 | UNPACKING I-CONNECT AND APPLYING THE WRONG SERIAL KEY/LICENSE KEY DOES NOT RESULT IN A RETURN CODE OF <> 0 FROM PKGADD |
134248 | ICONNECT SILENT INSTALL DOES NOT WORK AS EXPECTED |
147897 | INSTALLATION OF I-CONNECT 2.6 FAILS ON LINUX |
I-CONNECT
110741 | CONNECT - ON WIN95 IF ONE DOES NOT LOGIN WITH THE WINDOWS LOGIN PROPMT RUNNING ILOGIN GETS A 25590 ERROR. LOGIN AND SAME CONNECTION WORKS FINE |
II Known Issues with CSDK 2.80 release
ESQL/C
151008 | SHARED LIBRARIES ARE BEING CREATED WITHOUT PASSING -LC TO THE LINKER IN CSDK2.70 |
155195 | ESQL/C GENERATES CODE WHICH IS NOT CONST CORRECT - PROBLEMS WITH PROTOTYPES IN SQLHDR.H AND SO ON |
ODBC
154992 | CAN'T INSERT SOME SJIS CODE THROUGHT ODBC 3.80 |
155570 | RACE CONDITION EXISTS WHERE CONNECTIONS TO MULTIPLE DISTINCT INSTANCES CAN OVERWRITE EACH OTHER CORRUPTING THE CONNECTION STRING. |
155934 | COM OBJECTS THAT OPEN MORE THAN ONE CONNECTION IN A OBJECTCONTEXT RECEIVE A -6 WHEN CALLING XA_END |
156211 | USING MS ACCESS PASS THROUGH QUERY TO RUN A LARGE QUERY (24K), WHICH HAS MANY SELECT STATEMENTS, (ABOUT 80), GIVES RESERVED ERROR -7711. |
156251 | USING ANSI SYNTAX FOR LEFT OUTER JOIN WITH THE THE OJ SYNTAX GENERATES A -393 ERROR MESSAGE WITH ODBC |
OLEDB
155650 | ERROR 'CONNECTION FAILED' FROM MICROSOFT ANALYSIS MANAGER (PART OF MICROSFT SQL SERVER 2000) WHEN CONNECTING USING OLEDB |
156187 | WHEN STARTING A TRANSACTION IN MTS IT DOES NOT EVEN APPEAR IN THE DTC COORDINATOR |
156248 | INSERT STATMENT GIVING ERROR OF -206, IT DOESN'T QUERY DATABASE |