|
Problem IC67459
|
Status: Closed |
CREATE EVENT MONITOR DDL MAY ABNORMALLY TERMINATE WITH SQL1224N |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The CREATE EVENT MONITOR DDL statement allows you to specify the
name of the unformatted event table. If the name specified is
an alias, 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).
0x00002B31A7C83009 sqloEDUCodeTrapHandler + 0x0273
(/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00002B31A43EAC10 address: 0x00002B31A43EAC10 ; dladdress:
0x00002B31A43DD000 ; offset in lib: 0x000000000000DC10 ;
(/lib64/libpthread.so.0)
0x00002B31A87BE615
_Z22sqlrl_evmon_eventtableP8sqlrr_cbPhsbP17sqlrl_evmon_parms +
0x14d3
(/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00002B31A87BB9EF
_Z23sqlrlCreateEventMonitorP8sqlrr_cbP9sqlm_empdP11sqlrrstringP1
7sqlrl_evmon_parms
+ 0x0d3d
(/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00002B31A70EA965 _Z26sqlnq_ddl_create_evmon_endv + 0x1537
(/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00002B31A70E9391
_Z23sqlnq_create_evmon_stmtPP8stknode_i10actiontypePhP3loc +
0x0215
(/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00002B31A6D9F22E _Z12sqlnp_smactnP8sqlnp_cbi + 0x11a4
(/home/db2inst1/sqllib/lib64/libdb2e.so.1) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Version 9.7 GA through Fix Pack 1 servers on Linux, *
* Unix and Windows environments. Those who specify an *
* unformatted event table name explicitly in their CREATE *
* EVENT MONITOR statements may experience this problem. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Logic in CREATE EVENT MONITOR DDL does not account for all *
* possible values that may exist in the system catalog tables. *
* Not checking appropriately will lead to abnormal *
* termination of the program. *
****************************************************************
* RECOMMENDATION: *
* Specify base table names explicitly when providing the *
* unformatted event table names or apply DB2 Version v9.7 Fix *
* Pack 2. *
**************************************************************** |
| Local Fix: |
Use the base table name directly when explicitly specifying the
name of the unformatted event table. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 Version 9.7 Fix Pack 2 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67475 IC68571
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.03.2010
23.04.2010
23.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
