|
Problem IC73661
|
Status: Closed |
Crash or unexpected behavior may happen as a result of wrong post-compile optimization logic |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
If you get crashes or unexpected behavior, this APAR could be at
fault.
One of the scenarios when this issue can happen is if you are
using compiled triggers.
If you are using DB2MEMDBG db2set regisrty, in the case of
compiled triggers, the stack may be similar to:
sqlriMemValidate
sqlriValidateSection
sqlriSectInvoke
sqlrr_process_execute_request
sqlrr_execute
sqljs_ddm_excsqlstt
sqljsParseRdbAccessed
sqljsParse |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Statements involving compiled SQL triggers. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Crash if DB2MEMDBG options is used, or wrong results, due to *
* section memory overwrite because of use of compiled SQL *
* triggers. *
****************************************************************
* RECOMMENDATION: *
* Apply 95FP8 with the fix. *
**************************************************************** |
| Local Fix: |
Apply code fix. |
| available fix packs: |
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 |
Apply 95FP8 with the fix. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.01.2011
27.06.2011
27.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
