Feedback
Did this article resolve your question/issue?

   

Article

With XQuery the catalog size is different depending on whether DB2 Accelerator is enabled

Information

 
TitleWith XQuery the catalog size is different depending on whether DB2 Accelerator is enabled
URL NameWith-XQuery-the-catalog-size-is-different-depending-on-whether-DB2-Accelerator-is-enabled
Article Number000184445
EnvironmentProduct: XQuery
Version: 5.0
OS: Java
Database: DB/2
Application: N/A
Question/Problem Description
With XQuery the catalog size is different depending on whether DB2 Accelerator is enabled.   For example, when query Accelerator is enabled it results in a catalog size of 4.8MB where as 12 MB is expected.
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberPSC00344122
Enhancement Number
Cause
The communication between the underlying DB/2 JDBC driver and the DB/2 database is different when Accelerator is enabled.  The driver was not designed to handle all aspects of communication where query acceleration is enabled on the server.
Resolution
Fixed in hotfix of XQuery 5.0 that contains version 5.1.4.0160 or higher of the JDBC DB/2 driver

Refer to "DataDirect XQuery hot fix download and install instructions" for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date2/26/2016 9:23 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.