|
Problem IC87917
|
Status: Closed |
SQLDESCRIBEPARAM() MAY FAIL WITH CLI0150E DRIVER NOT CAPABLE WHEN CALLING AN UNQUALIFIED STORED PROCEDURE ON DB2 FOR Z/OS |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
When calling SQLDescribeParam() on a prepared statement for a
stored procedure running on DB2 for z/OS, it may fail with the
following error:
[IBM][CLI Driver] CLI0150E Driver not capable. SQLSTATE=HYC00
Stored procedures are qualified by adding the name of the schema
along with the stored procedure name. When the schema name is
not provided, it should qualify it with the connecting userid as
the default schema. The failure occurs when the stored procedure
is called without the schema name and the stored procedure
exists
under the connecting userid's schema. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* If a stored procedure is called without qualifying, the *
* stored procedure may fail with 'Driver not capable ' error. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product version v.97.fp7 *
**************************************************************** |
| Local Fix: |
When calling the stored procedure, ensure it is explicitly
qualified with the schema name. For example, "call
schema.storedprocedure()" instead of "call storedprocedure()" |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
18.12.2012
18.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
