home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC94183 Status: Closed

.NET EXCEPTION WHEN SERVER SIDE PAGINATION IS ENABLED WITH ODATA WITH
INFORMIX DATABASE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When OData is used with Informix database and when server side 
pagination is enabled, the application receive following 
exception: 
 
<message>ERROR [IX000] [IBM][IDS/UNIX64] Not implemented 
yet.</message> 
<type>IBM.Data.DB2.DB2Exception</type>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* IBM Data Server Driver users                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* N/A                                                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
N/A
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC97536 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.07.2013
28.10.2013
28.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList