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 IC80656 Status: Closed

DB2 CLIENT INCORRECTLY INVOKES SYSPROC.SQLPROCEDURECOLS() WHEN STORED
PROCEDURE WITH TIMESTAMP INOUT/OUT PARAMS ARE CALLED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 client invokes SYSPROC.SQLPROCEDURECOLS() when .NET 
application calls a stored procedures that contains INOUT/OUT 
timestamp parameters even when correct data types are bound. DB2 
clients should only call SYSPROC.SQLPROCEDURECOLS() when the 
application binds parameters with mismatched data types. 
 
The issue only happens against DB2 z/os 10 server. 
 
The extra call to SYSPROC.SQLPROCEDURECOLS() may degrade 
performance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 .Net application users                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 .Net application invokes SYSPROC.SQLPROCEDURECOLS()      * 
* internally even when correct data types are                  * 
* being bound in the application.                              * 
*                                                              * 
* Problem only happens with stored procedures that contain     * 
* INOUT/OUT                                                    * 
* timestamp parameters and against DB2 z/os 10 server.         * 
*                                                              * 
* The extra call of SYSPROC.SQLPROCEDURECOLS() may cause       * 
* performance degradation.                                     * 
*                                                              * 
* DB2 clients should only call SYSPROC.SQLPROCEDURECOLS() when * 
* application binds parameters with mismatched data types.     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP6                                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in V9.7 Fixpak 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC83844 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.01.2012
11.07.2012
11.07.2012
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList