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

STORED PROCEDURE MAY FAIL WITH SQL30073N WHEN THERE ARE 10780 PARAMETER
MARKERS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Application receives the following error while executing a 
stored procedure. 
 
SQL30073N  "0x0000" Parameter value "0x0000" is not supported. 
SQLSTATE=58017 
 
The error only occurs when the stored procedure has 10780 
parameter markers.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V97FP2                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Application receives the following error while executing a   * 
*                                                              * 
* stored procedure.                                            * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL30073N  "0x0000" Parameter value "0x0000" is not          * 
* supported.                                                   * 
* SQLSTATE=58017                                               * 
*                                                              * 
*                                                              * 
*                                                              * 
* The error only occurs when the stored procedure has 10780    * 
*                                                              * 
* parameter markers.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP3                                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 DB2 V9.7 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.04.2010
24.09.2010
24.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList