| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC95230 | Status: Closed |
CREATE EVENT MONITOR FAILS WITH SQL0604N ON "BLOB (32) INLINE LENGTH 32" | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
Creating an event monitor might fail on activity tables in
table space of 16k page size :
% db2 "CREATE EVENT MONITOR MY_WLM_ACTIVITIES FOR ACTIVITIES
WRITE TO TABLE
ACTIVITY (TABLE MYTOOLS.ACTIVITY_WLM_ACTIVITIES IN
MYEVENTMON ),
ACTIVITYSTMT (TABLE MYTOOLS.ACTIVITYSTMT_WLM_ACTIVITIES IN
MYEVENTMON ),
ACTIVITYVALS ( TABLE TOOLS.ACTIVITYVALS_WLM_ACTIVITIES IN
MYEVENTMON )
AUTOSTART"
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0604N The length, precision, or scale attribute for column,
distinct type,
structured type, array type, attribute of structured type,
routine, cast
target type, type mapping, or global variable "BLOB (32) INLINE
LENGTH 32" is
not valid. SQLSTATE=42611 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Using event monitors * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.5 FP3 * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in version 10.5 FP3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 27.02.2014 27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.3 |
|
| 10.5.0.3 |
|