DB2 - Problembeschreibung
Problem IC96234 | Status: Geschlossen |
CLI0113E ERROR OCCURS ON TIMESTAMP LITERAL VALUE FOR OUTPUT PARAMETER OF STORED PROCEDURE WHEN IMPLICIT CAST IS DISABLED | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problembeschreibung: | |
The following error may occur from a CLI/ODBC application when calling a stored procedure with a timestamp supplied as a literal value for an output parameter: CLI0113E Invalid date/time format This works fine when when the implicit cast feature is enabled but when it is disabled (via DB2 for z/OS APAR PM77180), and any datatype mismatch, server hit -301 error and cli will retry. while retrying validation is being done on the timestamp literal value that is supplied for the output parameter. If the value supplied is not a valid timestamp value (For example, an empty string '') the CLI0113E error will occur. This APAR will replace the output literal value to a null indicator even when the parameter is not bound but has the values supplied during call. This will avoid the CLI0113E error | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL DB2 CLI users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2_v97fp9 and later * **************************************************************** | |
Local-Fix: | |
As a workaround, supply a value for the timestamp output parameter that has a valid timestamp format. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
fixed in db2_v97fp9 and later | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC96713 IC96874 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 25.09.2013 18.12.2013 18.12.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
9.7.0.9 | |
9.7.0.9 |