suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT21412 Status: Closed

INSTANCE CRASH EVENT MONITOR WHEN PERFORMING A LOAD VIA CURSOR

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Instance can crash as a result of memory corruption if you have
the following:

- Event Monitor Created & Enabled.
- LOAD FROM CURSOR with a very large SQL Statement (~ 16KiB text
and larger).

As this is memory corruption the faulting stack may vary but is
likely to include event
monitor and/or fast writer functions. An example may be:

generateEvent__18sqmEvmonGenFactoryXT19
   sqmEvmonType_policyXSP17SP47SP25SP8_T37
   sqmEvmonUtilLocation_Collector_policy_FP19sqmFastWriterRecord
+ 0xF00
collectEventData__34sqmEvmonUtilStart_Collector_policyFCPC9sqeBs
   uEduR15sqmRecordHelperCP19sqmFastWriterRecord + 0xFF8
generateEvent__18sqmEvmonGenFactoryXT19sqmEvmonType_policyXSP17S
   P44SP23SP8_T34sqmEvmonUtilStart_Collector_policy_Fv + 0xC84
sqmGenerateLoadStartEvent__FCP8sqlrr_cbP26
   sqluCLoadRequestDescriptorP20SQLU_LOADAPI_LOAD_CBP20
   sqlmUtilInvocationIDb + 0x374
sqlu_register_table_load__FP26sqluCLoadRequestDescriptorP24
   sqlusCLoadMPPCoordinatorP15sql_static_dataPb + 0x1A48
iRun__24sqlusCLoadMPPCoordinatorFv + 0x80
...

It may also trap and fail to produce a stack trace with the
reported si_addr being the
hexadecimal representation of an ASCII string.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All Platforms                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 LUW v10.5 Fixpack 10 or later.                *
****************************************************************
Local Fix:
The issue can be avoided by:
- Reducing the SQL Statement text size in the CURSOR.
- Disable the Event Monitors.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT21440 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.07.2017
16.07.2018
16.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)