|
Problem IC68571
|
Status: Closed |
CREATE EVENT MONITOR DDL MAY ABNORMALLY TERMINATE WITH SQL1224N |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
The CREATE EVENT MONITOR DDL statement allows you to specify the
name of the event table. If the name specified is an alias or
view, instead of an actual table, DB2 will abnormally terminate
with SQL1224N. Instead, it should gracefully return a SQL0601N
error.
You can identify this problem by matching the following stack in
the trap file generated in the FODC directory under the
diagnostic data directory path (DIAGPATH).
0x090000002837F93C sqlrrSqlCode + 0x39C
0x0900000028DEA6CC
sqlrl_evmon_eventtable__FP8sqlrr_cbPUcUsT3P17sqlrl_evmon_parms +
0xDCC
0x0900000028DEB620
sqlrlcre__FP8sqlrr_cbP9sqlm_empdP11sqlrrstringP17sqlrl_evmon_par
ms
+ 0xC00
0x0900000046357770 sqlnq_ddl_create_evmon_end__Fv + 0x10B0
0x0900000046357B00
sqlnq_create_evmon_stmt__FPP8stknode_i10actiontypePUcP3loc +
0x280 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Version 9.5 GA through Fix Pack 5 servers on *
* Linux,Unix and Windows environments. Those who specify *
* anevent table name explicitly in their CREATEEVENT MONITOR *
* statements may experience this problem. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Logic in CREATE EVENT MONITOR DDL does not account for *
* allpossible values that may exist in the system catalog *
* tables.Not checking appropriately will lead to *
* abnormaltermination of the program. *
****************************************************************
* RECOMMENDATION: *
* Specify base table names explicitly when providing theevent *
* table names or apply DB2 Version v9.5 FixPack 6. *
**************************************************************** |
| Local Fix: |
Use the base table name directly when explicitly specifying the
name of the event table. |
| available fix packs: |
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
|
| Solution |
Problem is first fixed in DB2 Version 9.5 Fix Pack 6 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.05.2010
31.05.2010
31.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
