Informix - Problem description
Problem IT01588 | Status: Closed |
CHANGE DATA CAPTURE SMART LARGE OBJECT READ PSEUDO CODE WRONG FOR .NET DRIVER | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
http://www-01.ibm.com/support/knowledgecenter/SSGU8G_12.1.0/com. ibm.cdc.doc/ids_cdc_055.htm?lang=en Smart large object read function for the IBM Informix .NET Provider is documented wrong. The smart large object read function for .NET works differently than for other client APIs. The following pseudo code illustrates the basic structure for reading smart large objects with .NET: conn = new IfxConnection(..)// to SYSCDC database execute function informix.cdc_opensess() // on the same connection IfxBlob( IfxConnection connection )// construct it using the same connection IfxBlob.Open(ReadOnly) // open it IfxBlob.Read(char[] buff) <<< This is Wrong This IfxBlob.Read() is wrong Should be: IfxBlob.Read(long plofd, byte[] buff) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Informix 11.70, 12.10 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See problem conclusion. * **************************************************************** | |
Local Fix: | |
Solution | |
The following corrected pseudo code illustrates the basic structure for reading smart large objects with .NET: conn = new IfxConnection(..)// to SYSCDC database execute function informix.cdc_opensess() // on the same connection IfxBlob( IfxConnection connection )// construct it using the same connection IfxBlob.Open(ReadOnly) // open it IfxBlob.Read(long plofd, byte[] buff) | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.05.2014 16.10.2015 16.10.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
12.10.xC5 | |
12.10.xC5.W1 |