DB2 - Problembeschreibung
Problem IC99191 | Status: Geschlossen |
DB2CAEM FAILS IF THE SQL INPUT CONTAINS A COMMENT "--" WHICH IS NOT AT THE START OF A LINE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
V101FP4 contains fix. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC99235 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 05.02.2014 03.06.2014 03.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |