DB2 - Problem description
Problem IC65108 | Status: Closed |
USING PRIOR AS A COLUMN NAME WILL GIVE SQL0104N ALTHOUGH DB2_COMPATIBILITY_VECTOR IS NOT SET | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The following SELECT will return SQL0104N: SELECT prior FROM tab1; PRIOR should only be handled as a reserved keyword, when DB2_COMPATIBILITY_VECTOR has bit x08 set. | |
Problem Summary: | |
USERS AFFECTED: All PROBLEM DESCRIPTION: See ERROR DESCRIPTION PROBLEM SUMMARY: See ERROR DESCRIPTION | |
Local Fix: | |
* Put the column name PRIOR under double quotes * Use fully qualified column names | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 2 | |
Workaround | |
See LOCAL FIX. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67557 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.12.2009 08.06.2010 08.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |