DB2 - Problem description
Problem IC83844 | Status: Closed |
DB2 CLIENT INCORRECTLY INVOKES SYSPROC.SQLPROCEDURECOLS() WHEN STORED PROCEDURE WITH TIMESTAMP INOUT/OUT PARAMS ARE CALLED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
DB2 client redundantly invokes SYSPROC.SQLPROCEDURECOLS() when .net application calls stored procedures that contain INOUT/OUT timestamp parameters. Even when correct data types are being bound in the application. DB2 clients should only call SYSPROC.SQLPROCEDURECOLS() when application binds parameters with mismatched data types. The issue only happens against DB2 z/os 10 server. The extra call of SYSPROC.SQLPROCEDURECOLS() costs performance degradation. | |
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 V10.1FP1 or later releases. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in V10.1 Fixpak 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.05.2012 06.11.2012 06.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |