DB2 - Problem description
| Problem IT09456 | Status: Closed |
IMPROVE THE HANDLING FOR RECURSIVE TRIGGER | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
When a recursive trigger is invoked, it may take a very long time for the triggering insert, update or delete statement to compile. The db2agent cannot be forced off at that time even though the application process has been killed. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * User who use recursive trigger in db2 v10.5 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 v10.5 fixpack 7 or above * **************************************************************** | |
| Local Fix: | |
set a lower value to STMTHEAP can make the statement fail earlier | |
| Solution | |
The problem is first fixed in db2 v10.5 fixpack 7 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.06.2015 20.01.2016 20.01.2016 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.7 |
|