DB2 - Problem description
Problem IC86039 | Status: Closed |
SQL0804N MAY BE RETURNED WHEN A WLM SQLROWSREAD THRESHOLD IS VIOLATED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Problem Description: When a WLM SQLROWSREAD threshold is defined with the action CONTINUE (possible actions are STOP EXECUTION, CONTINUE, FORCE APPLICATION) it's expected that execution of the current activity will continue. However, in this case the error SQL0804N is returned when the threshold is violated and the query fails. The solution for this problem ensures the threshold report generated during the threshold violation is ignored during execution of the query. As a result the SQL0804N error will not be returned to the user or application. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * WLM users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 8. * **************************************************************** | |
Local Fix: | |
Possible workaround: It's possible to avoid the SQL0804 error by increasing the number of rows specified in SQLROWSREAD threshold. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 8. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC91720 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.08.2012 04.04.2013 04.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |