DB2 - Problem description
| Problem IC99191 | Status: Closed |
DB2CAEM FAILS IF THE SQL INPUT CONTAINS A COMMENT "--" WHICH IS NOT AT THE START OF A LINE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
db2caem fails if the SQL input contains a comment "--" which is
not at the start of a line
For example:
Sample SQL statement: "select -- test * -- test1 from t1"
DBT7028E "db2caem": The db2caem command failed because the DB2
database manager encountered an error while processing the
specified input parameters and the specified SQL statement.
Handle type: "3". Return code: "-1:1945".
CLIInfo: SQLstate: "42601"
Return code: "-104"
Diagnostic message: "[IBM][CLI
Driver][DB2/LINUXX8664] SQL0104N An unexpected token
"END-OF-STATEMENT" was found following " ". Expected tokens may
include: "JOIN <joined_table>". SQLSTATE=42601
"
DBT7033E "db2caem": The db2caem utility encountered an error
while processing the specified SQL statement. SQL statement:
"select -- test * -- test1 from t1". Return code: "-1:4008". | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V101FP4 * **************************************************************** | |
| Local Fix: | |
Modify the input SQL so it doesn't have a comment "--" which is not at the start of a line | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
| Solution | |
V101FP4 contains fix. | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC99235 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.02.2014 03.06.2014 03.06.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.4 |
|