Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC62298 Status: Geschlossen

Create table event monitor statement with "trunc" keyword may
fail with SQLCODE -104

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
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
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
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.07.2009
17.02.2010
17.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP5
Problem behoben lt. FixList in der Version
9.5.0.5 FixList