|
Problem IC61812
|
Status: Closed |
STORED PROCEDURE EXPLAIN_SQL WITH CURRENT SCHEMA INPUT PARAMETER RETURNS SQLCODE -713 |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
Stored procedure EXPLAIN_SQL returns the following sqlca when
CURRENT SCHEMA is passed as an input parameter:
SQLCA Information
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -713 sqlerrml: 14
sqlerrmc: CURRENT SCHEMA
sqlerrp : SQLNQ1CC
sqlerrd : (1) -2145779603 (2) 0 (3) 0
(4) 0 (5) -100 (6) 0
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 42815 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* After explaining the sql query, the stored procedure *
* EXPLAIN_SQL resets the original value of DB2 special *
* registers. While resetting the value of CURRENT SCHEMA it *
* passes a long schema name, most of which is blank character. *
* The schema name is found invalid by the db2 engine because *
* it is longer than the supported length of schema names. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product Version 9.1 Fix Pack 8. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Problem was first fixed in Version 9.1 Fix Pack 8. The schema
name is truncated if its length exceeds 30 characters, which is
the maximum length allowed for a schema name. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC64041 IC64286 IC64694
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.06.2009
27.10.2009
27.10.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.8
|
 |
