DB2 - Problem description
| Problem IC64385 | Status: Closed |
OPTIMIZATION PROFILES WITH SCHEMA NAMES CONTAINING # CHARACTERS WILL REPORT EXP0037W IN THE EXPLAIN EXTENDED DIAGNOSTIC SECTION | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
The following STMTKEY in a optimization profile, where the
SCHEMA name contains a # character:
<STMTKEY SCHEMA="S#AMPLE"> ...
</STMTKEY>
Reports EXP0037W in the generated db2expln output:
Extended Diagnostic Information:
--------------------------------
Diagnostic Identifier: 1
Diagnostic Details:
EXP0037W Invalid setting request. The schema at
line "2", column "31" is not a correct identifier
(schema names should not have leading or traling
white spaces unless delimited strings).
Nevertheless, the optimization profile is applied for the given
SQL statement. | |
| Problem Summary: | |
USERS AFFECTED: All PROBLEM DESCRIPTION: See ERROR DESCRIPTION PROBLEM SUMMARY: See ERROR DESCRIPTION | |
| Local Fix: | |
Delimit the SCHEMA name with " in the optimization profile, when it contains a # character: <STMTKEY SCHEMA=""S#AMPLE""> | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in Version 9.7 Fix Pack 3. | |
| Workaround | |
See LOCAL FIX. | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.11.2009 24.09.2010 24.09.2010 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.3 |
|
| 9.7.0.3 |
|