IBM Support

IBM Security Guardium : "is null" operator usage in query conditions for reports

Question & Answer


Question

Why do my reports bring inconsistent data with same query conditions ?

Cause

This might happen if improper comparison operators are used for some known attributes in Guardium reporting.
This is not a defect in the product, it is the behavior of the sql comparison operators for MySQL which is internal DB of Guardium Appliance.

Comparison with % will fetch the results with something OR blank values but it won't fetch the values which are NULL.

Answer

This technote documents the use of "is null" operator for the known attributes in query conditions of the reports.

There are certain attributes in report with which the comparison with % (i.e. wildcard character for ANYTHING) might bring inconsistent results.

To make sure even the null values are considered in reporting for some known attributes, it is suggested that the query conditions for reports be modified as:

compare with IS NULL OR with %, so that all the needed results will be included in the output of the report.

Sample :
(
ANALYZED_CLIENT_IP is NULL
or
ANALYZED_CLIENT_IP like parameter XXX
)

Known Attributes that might contain NULL values



[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Documentation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"10.0;10.0.1;10.1;10.1.2;9.0;9.1;9.5","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg22002339