Troubleshooting
Problem
You have installed an STAP and have databases running but Guardium is not automatically populating inspection engine (IE) settings. When you run Discovery, no IEs are created.
Cause
The discovery parameter is not enabled.
Diagnosing The Problem
If GIM is used to install the STAP, Discovery should run once initially.
The discovery setting should be a list of supported databases like the following (some values may not be included depending on S-TAP version):
oracle:db2:informix:mysql:postgres:sybase:hadoop:teradata:netezza:memsql:mariadb
In the STAP configuration file guard_tap.ini, check "discovery_dbs".
In the STAP configuration file guard_tap.ini, check "discovery_dbs".
In GIM, check the parameter "STAP_DISCOVERY_DBS".
To turn off Discovery, set the value to NULL, e.g. "discovery_dbs=NULL".
To turn off Discovery, set the value to NULL, e.g. "discovery_dbs=NULL".
Resolving The Problem
How to Run Discovery
After you have set the parameter, you must re-run Discovery.
On the database server, run this manually:
For guard_tap.ini, set discovery_debug=1.
Then re-run Discovery per the instructions above.
1. <STAP install directory>/guard_stap/guard_discovery <STAP install directory>/guard_stap/guard_tap.ini --update_tap
2. Restart STAP
In the GUI, navigate to: Manage > Activity Monitoring > S-TAP Control >
Select the S-TAP "Command" ("G" icon) > select Run Database Instance Discovery in the drop-down and check the box to write the inspection engine settings.
If Discovery does not produce the expected results, turn on Discovery debug.
In the GUI, navigate to: Manage > Activity Monitoring > S-TAP Control >
Select the S-TAP "Command" ("G" icon) > select Run Database Instance Discovery in the drop-down and check the box to write the inspection engine settings.
If Discovery does not produce the expected results, turn on Discovery debug.
For guard_tap.ini, set discovery_debug=1.
For GIM, set the parameter DISCOVERY_DEBUG to 1.
Then re-run Discovery per the instructions above.
The Discovery log can reviewed by taking an S-TAP Diagnostic and looking at the guard_discovery log for details on what it is searching for and what it found. Provide this diagnostic if you have to contact Support.
You can control how often Discovery runs by setting the value to the frequency in hours that you want it to run. The default is once a day or every 24 hours.
In guard_tap.ini, set "discovery_interval".
In guard_tap.ini, set "discovery_interval".
In GIM, the parameter is "STAP_DISCOVERY_INTERVAL".
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCJM6A","label":"IBM Security Guardium S-TAP for IMS on z\/OS"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
24 August 2020
UID
ibm16258719