IBM Informix RELEASE NOTES FOR IBM Informix LOB Locator DataBlade Module 1.20.UC2 2.00.xC2, January, 2004 ================================= TABLE OF CONTENTS I. OVERVIEW OF RELEASE NOTES II. NEW FEATURES III. IBM INFORMIX DYNAMIC SERVER COMPATIBILITY IV. REGISTERING THE LOB LOCATOR DATABLADE MODULE V. UNREGISTERING THE LOB LOCATOR DATABLADE MODULE VI. KNOWN PROBLEMS AND WORKAROUNDS +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I. OVERVIEW OF RELEASE NOTES ============================= The purpose of these release notes is to make you aware of any special actions required to register, configure, and use the LOB Locator DataBlade module on your computer. This file also describes new features and feature differences from earlier versions of this product and other IBM Informix products, and how these differences affect current products. In addition, this file contains information about known bugs and their workarounds. These release notes are written for the following audience: o System administrators who install IBM Informix Dynamic Server and the LOB Locator DataBlade module o Database administrators who control access to IBM Informix Dynamic Server databases o Developers who write applications using the LOB Locator DataBlade module II. NEW FEATURES ================= Version 1.20.UC2 of the LOB Locator DataBlade module was created with Version 3.5 of the DataBlade Developers Kit (DBDK). Previous versions of the DataBlade module were created with Version 3.2 of DBDK. III. IBM INFORMIX DYNAMIC SERVER COMPATIBILITY =============================================== Version 1.20.UC2 of the LOB Locator DataBlade module is compatible with IBM Informix Dynamic Server Version 9.13.UC3 or later. IV. REGISTERING THE LOB LOCATOR DATABLADE MODULE ================================================= To use the LOB Locator DataBlade module, you must register it using BladeManager in each database in which it will be used. See the "BladeManager User's Guide" for instructions on how to register DataBlade modules. NOTE: You cannot register the LOB Locator DataBlade module into an ANSI- compliant database. This is because BladeManager does not currently support the registration of any DataBlade module into ANSI-compliant databases. V. UNREGISTERING THE LOB LOCATOR DATABLADE MODULE ================================================== Unregistration removes the definitions for a DataBlade module's user- defined data types and routines. You can unregister a DataBlade module that was previously installed only if there is no data in your database that uses the definitions defined by the DataBlade module. This means, for example, that if a table is currently using the LLD_Locator data type, you will not be able to unregister the LOB Locator DataBlade module from your database. Unregistration is only available for modules that were registered with BladeManager. Refer to the "BladeManager User's Guide" for instructions on how to unregister DataBlade modules. VI. KNOWN PROBLEMS AND WORKAROUNDS =================================== This section describes known problems and workarounds. A. UNIMPLEMENTED FUNCTIONS --------------------------- Bug 65913 The following two functions, described in the "LOB Locator DataBlade Module Programmer's Guide," are not implemented in this release: o lld_create_client o lld_delete_client Calling either of these functions will generate a syntax error. Attempts to use the SQL versions of these functions generate the following error: 674: Routine (lld_create_client) can not be resolved. Attempts to use the API versions of these functions generate the following error when an attempt is made to load the shared object referencing this function: 9793: User Defined Routine (myudr) module load failed. The following error will appear in the online log file: 09:05:54 Loading Module 09:05:54 (6): C Language Module can't load ld.so.1: oninit: fatal: relocation error: symbol not found: lld_create_client: referenced in /tmp/myudr.so 09:05:54 (-1): ERROR: Loading Module If a shared object contains multiple UDRs and only one of those UDRs attempts to call lld_create_client, none of the UDRs in that shared object can be loaded. B. INTERFACE EXCEPTIONS ------------------------ The API and ESQL interfaces, described in the manual, generate these exceptions: o API Interface: Attempting to seek a smartblob (IFX_BLOB or IFX_CLOB) to an invalid offset using lld_seek generates an exception rather than returning LLD_E_OFFSET as expected. o ESQL/C Interface: If an lld_* function returns LLD_E_SQL, the corresponding SQLCODE or SQLSTATE can not be trusted as documented. Contact support: http://www.ibm.com/software/data/informix/ids/support/ (C) Copyright IBM Corp. 1996, 2012