DB2 - Problem description
Problem IT18970 | Status: Closed |
AUTOMAINT_SET_POLICYFILE DOESN'T REPORT ERROR WHEN FILTERCLAUSE SPECIFIED IS TOO LONG | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
System procedures SYSPROC.AUTOMAINT_SET_POLICY and SYSPROC.AUTOMAINT_SET_POLICYFILE returns successfully without any error even though the specified FilterClause is too long. However, the healthy monitor cannot accept such long FilterClause may cause the policy doesn't work at all. The following message shows the policy doesn't work: 2016-12-23-04.26.08.568934-300 E193001E581 LEVEL: Error PID : 8788 TID : 140502028048128 PROC : db2acd 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPID : *LOCAL.db2inst1.161223092611 HOSTNAME: SLES3 FUNCTION: DB2 UDB, Automatic Table Maintenance, atmRefreshInfoTable,probe:430 DATA #1 : String, 11 bytes AutoStats: DATA #2 : String, 144 bytes [IBM][CLI Driver][DB2/LINUXX8664] SQL0010N The string constant beginning with "'BCA" does not have an ending string delimiter. SQLSTATE=42603 DATA #3 : String, 5 bytes 42603 After the fix, SYSPROC.AUTOMAINT_SET_POLICY and SYSPROC.AUTOMAINT_SET_POLICYFILE returns error message so the user can know what is going wrong. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * n/a * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v11.1 or v11.5 with the latest fixpack level. * **************************************************************** | |
Local Fix: | |
Prevent from specifying too long FilterClause. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : follow-up : IT27040 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.01.2017 12.03.2020 12.03.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |