home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC91720 Status: Closed

SQL0804N MAY BE RETURNED WHEN A WLM SQLROWSREAD THRESHOLD IS VIOLATED.

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 Fix Pack 3.                      * 
****************************************************************
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 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList