|
Problem IC94460
|
Status: Closed |
CHANGE HISTORY EVENT MONITOR CAN CAUSE INSTANCE ABEND WHEN USING LOAD FROM CURSOR WITH LONG SQL |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When a load from cursor is used and the SQL statement text used
to declare the cursor is large ( > 16k bytes )
There can be an instance crash if the Change History event
monitor is enabled e.g. :
db2 "CREATE EVENT MONITOR CHGHIST FOR CHANGE HISTORY WHERE
EVENT IN (ALL) WRITE TO TABLE"
db2 " SET EVENT MONITOR CHANGE_HISTORY STATE 1"
A stack trace may have this :
generateEvent__18sqmEvmonGenFactoryXT19sqmEvmonType_p
collectEventData__34sqmEvmonUtilStart_Collector_poli
generateEvent__18sqmEvmonGenFactoryXT19sqmEvmonType_
sqmGenerateLoadStartEvent__FCP8sqlrr_cbP26sqluCLoadR
sqlu_register_table_load__FP26sqluCLoadRequestDescri
sqluvtld_route_in__FP12SQLE_DB2RA_T
...
but could vary depending on the size and the extent of the
memory overwrite that triggers the trap. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
Reduce the size of SQL statement e.g. by declaring some views.
Disable the Change history event monitor: db2 " SET EVENT
MONITOR CHANGE_HISTORY STATE 0"
for the duration of the load. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.07.2013
21.10.2014
21.10.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
|
|
