|
Problem IC96713
|
Status: Closed |
CLI0113E ERROR OCCURS ON TIMESTAMP LITERAL VALUE FOR OUTPUT PARAMETER OF STORED PROCEDURE WHEN IMPLICIT CAST IS DISABLED |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 CLI users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to v10.5.3 and later *
**************************************************************** |
| Local Fix: |
As a workaround, supply a value for the timestamp output
parameter that has a valid timestamp format. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
fixed in v10.5.3 and later |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2013
09.09.2014
09.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
