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

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

product:
DB2 NET SEARCH / 5765F3803 / 950 - 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:
The upper limit for MaskResolutionLimit parameter is set to a 
very low value. The limit specifies teh maximum number of terms 
that a wild card search term can be expanded into for searching. 
This is now increased to 500,000 such that customers receive the 
complete result set without truncation/error.
Local Fix:
Increase the number of characters in the serch.
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Upgrade to V95fp8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC75407 IC75408 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.03.2011
14.07.2011
14.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList