IBM Support

Guardium GUI does not show the valid protocol names for adding an inspection engine

Troubleshooting


Problem

When the Guardium GUI user tried to add an inspection engine for the target DB server, you may notice that the target DB names such as DB2 or Oracle are not found as the protocol name. As a result, any Guardium GUI user cannot select an appropriate protocol name and cannot add an inspection engine for the target DB server.

Symptom

After Guardium GUI login, the following GUI steps may show you that insufficient DB protocol names are listed.

1. Administration Console

2. Configuration

3. Inspection Engines

4. Add Inspection Engine

5. go to Protocol

or

1. Administration Console

2. Local Taps

3. S-TAP Control

4. Edit S-TAP Configuration

5. Add Inspection Engine

6. go to Protocol

Therefore any GUI user cannot define a new inspection engine for the target DB.

Restarting gui or system is also not able to resolve this situation.

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Guardium Database Activity Monitor","Platform":[{"code":"PF016","label":"Linux"}],"Version":"9.1;9.0;8.2","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
04 September 2019

UID

swg21680067

Page Feedback