|
Problem IC64384
|
Status: Geschlossen |
OPTIMIZATION PROFILES WITH SCHEMA NAMES CONTAINING # CHARACTERS WILL REPORT EXP0037W IN THE EXPLAIN EXTENDED DIAGNOSTIC SECTION |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
USERS AFFETCED:
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""> |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in Version 9.5 Fix Pack 6. |
| Workaround |
See LOCAL FIX. |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC64385 IC68332
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 06.11.2009
10.09.2010
10.09.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP6
|
| Problem behoben lt. FixList in der Version |
