home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66958 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users prior to V9.5 FP6                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Application receives the following error while executing     * 
* astored procedure.SQL30073N  "0x0000" Parameter value        * 
* "0x0000" is notsupported.SQLSTATE=58017The error only occurs * 
* when the stored procedure has 10780parameter markers.        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 FP6                                          * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in V9.5 FP6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67682 IC68053 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.03.2010
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version