Queries within Web Console Find pages/ Custom Reports are case sensitive

  • Document ID:3194122
  • Creation Date:06-Mar-2007
  • Modified Date:27-Apr-2012
    • Micro Focus Products:
      ZENworks Asset Management

Environment

Novell ZENworks 7.5 Asset Management - ZAM7.5
Novell ZENworks 7 Asset Management - ZAM7

Situation

Queries from the Web Console Find pages and in custom report criteria are case sensitive in Oracle installations. This is causing the user to have to determine upper/lower case format on strings that they wish to query for within custom reports; and having to create multiple reports for the same string if it is expressed in more than one way in the database. If customers are not aware of this, they get no results from queries if they don't match the case format
correctly.

Resolution

Fixed in ZAM 7.0 IR10.
Fixed in ZAM 7.5 IR 1
If downloading the Interim Release manually from the Novell support site, the filename is ZAM700SP1IR10.EXE or UPD750.ZIP for ZAM 7.5 IR1. The Interim releases can also be set up within the ZAM Manager for the Task server to check the site on a scheduled basis, and download and apply them automatically. Please refer to the Help Section for details of how to set up automatic downloads if desired.
Each interim release is cumulative. If Interim Release 10 is not available due to a later interim release being placed on the website, be assured that the code needed is in the later release.
Oracle 10G - ZAM 7.0 IR10 For users running 10g, the custom reports will be case insensitive when the following operators are used:

=
not =
in list
not in list
>
<
<=
>=

The FIND reports will be case-insensitive when the criteria does not contain wild cards (*).

Oracle 10.2 - ZAM 7.0 IR10All operators (in the custom reports and FIND reports) are case-insensitive.
This feature is going to be controlled with a configuration switch in RtrSetup.xml. The case insensitivity will only exist if the parameter "CaseInsensitiveSearches" is set to "yes". That is due to a potential significant performance cost to the case insensitive feature.

To turn the feature one, add this to RtrSetup.xml:

< param>
CaseInsensitiveSearches
yes