DB2 - Problem description
Problem IC62298 | Status: Closed |
Create table event monitor statement with "trunc" keyword may fail with SQLCODE -104 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
db2 create table event monitor statement with "trunc" keyword may fail with SQLCODE -104. Here is example of the error that may be encountered: >db2 -v "create event monitor dead for deadlocks with details history write to table stmthist (in allnodes trunc)" DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0104N An unexpected token "-" was found following "L,STMT_TEXT VARCHAR(". Expected tokens may include: "<space>". SQLSTATE=42601 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All platform * **************************************************************** * PROBLEM DESCRIPTION: * * db2 create table event monitor with "trunc" keyword may fail * * with SQL0104N. * * * * >db2 -v "create event monitor dead for deadlocks with * * details history write to table stmthist (in allnodes trunc)" * * DB21034E The command was processed as an SQL statement * * because it was not a * * valid Command Line Processor command. During SQL processing * * it returned: * * SQL0104N An unexpected token "-" was found following * * "L,STMT_TEXT VARCHAR(". * * Expected tokens may include: "<space>". SQLSTATE=42601 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.5 Fixpack 5 * **************************************************************** | |
Local Fix: | |
Don't use "trunc" keyword. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
V9.5 fixpack 5 will contain a fix to allow the create event monitor statement with trunc keyword to be processed successfully. | |
Workaround | |
Don't use trunc keyword | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.07.2009 17.02.2010 17.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.5 |