|
Problem IC68332
|
Status: Closed |
OPTIMIZATION PROFILES WITH SCHEMA NAMES CONTAINING # CHARACTERS WILL REPORT EXP0037W IN THE EXPLAIN EXTENDED DIAGNOSTIC SECTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - 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 Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.8 Fix Pack 4. *
**************************************************************** |
| 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.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
First fixed in DB2 Version 9.8 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.05.2010
05.08.2011
05.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
