home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC75406 Status: Geschlossen

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

Produkt:
DB2 NET SEARCH / 5765F3803 / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
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.
verfügbare FixPacks:
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

Lösung
Upgrade to V95fp8
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC75407 IC75408 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.03.2011
14.07.2011
14.07.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP8
Problem behoben lt. FixList in der Version
9.5.0.8 FixList