DB2 - Problem description
Problem IT34418 | Status: Closed |
QUERY INTERRUPT DOES NOT RETURN SQL0952N WHEN A WLM THRESHOLD WAS CREATED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
When using a Query Timeout with an application, the expected SQLCODE from the database server is -952 (Processing was cancelled due to an interrupt). However when a WLM threshold is created on the database server, it is possible that instead of returning an SQL0952N, the database returns an empty cursor instead. This could be true even if the WLM threshold has no impact on the SQL statement that is being timed out. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 or later * **************************************************************** | |
Local Fix: | |
Drop all WLM thresholds then reactivate the database. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 or later * **************************************************************** | |
Comment | |
Upgrade to 11.5.6 or later | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.10.2020 21.06.2021 21.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |