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 IC73382 Status: Geschlossen

SQL0901N/SQL16074N XML SUBTYPE IS NOT INITIALIZED WHEN CALLING STORED
PROCEDURE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Calling a SQL stored procedure using XML may return 
SQL0901/SQL16074 when its package is bound using REOPT=ALWAYS. 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "XML 
subtype is not 
initialized".) 
 
SQL16074N  An XQuery atomic value with the lexical 
representation starting 
with "                                              " of type 
"xs:string" cannot be processed in the XQuery operation or 
function "xs:float()" because the length exceeds the operation 
or function limit of "30" bytes.
Problem-Zusammenfassung:
See ERROR DESCRIPTION.
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem first fixed in v9.7 Fixpack 4.  At minimum this fix 
should be applied to the server.
Workaround
See LOCAL FIX.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC73389 IC73390 IC73392 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.12.2010
30.06.2011
30.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList
9.7.0.5 FixList