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 IT31755 Status: Closed

THE UPPER LIMIT FOR MASKRESOLUTIONLIMIT PARAMETER IS SET TO TOO LOW VALUE
- 10000

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
If a customer is using masking characters in his queries (e.g.
%wa%), this will only provide non-truncated results based on a
higher value set for either the preconfigured
MaskResolutionLimit  or the search query parameter EXPANSION
LIMIT.

Currently the upper limit for MaskResolutionLimit parameter is
set to a too low value -10000. An upper limit of 10000 for
MaskResolutionLimit will not give the desired results .The limit
specifies the maximum number of terms that a wild card search
term can be expanded into for searching. This should be
increased to 500,000 so that the customer can receive the
complete result set without truncation/error.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5m4fp0 or later                            *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT09227 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.02.2020
30.06.2020
30.06.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)