|
Problem IC77143
|
Status: Closed |
AN UPDATE QUERY ON A UNION ALL VIEW WITH TABLES HAVING TRIGGERS MAY CAUSE INSTANCE TO CRASH. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
An update query may cause database to crash if the following
conditions are met.
1. The update is on a UNION ALL view.
2. The underlying tables have triggers or other constraints
defined on them.
The result is a memory corruption with the following call stack:
0 sqlnq_qnc::refetch
1 sqlnr_optprep
2 sqlnr_optprep_action
3 sqlnr_comp
4 sqlnr_seq
5 sqlnr_rcc
6 sqlnr_exe
7 sqlnn_cmpl
8 sqlnn_cmpl
9 sqlra_compile_var
10 sqlra_find_var
11 sqlra_get_var |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See problem description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 970 fix pack 5 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 970 fix pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.06.2011
27.02.2012
27.02.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
