Linux S-TAP is not capturing Db2 exit traffic

Use the Db2 exit health check script to check and optionally fix the Db2 IE parameters.

Symptoms

Db2 Exit traffic is not getting reported to Guardium.

Causes

Incorrectly configured IE parameters can prevent Db2 Exit traffic from getting reported to the Guardium system.

Environment

Linux environment using Db2 Exit.

Resolving the problem

Use the Db2 exit script to check the Db2 IE configurations, and optionally to make any required fixes identified by the script. The script is located in the guard_stap bin directory. You can run it from anywhere with the full path. The script has two options: ./db2_exit_health_check.sh [ check | fix ]
By default it performs the health check only. The fix option rectifies any IE parameters errors identified by the script. The script runs a health check on each DB section, performing the following:
  1. Find exit ie in guard_tap.ini file
  2. Validate db_install_dir
  3. Find the db user and group
  4. Check if the db user is authorized
  5. Check if db_install_dir matches with DB2_HOME or DB2 HOME
  6. Check if DB2 EXIT LIB is in place correctly
  7. Check permission of DB2 EXIT LIB path and DB2 EXIT LIB
  8. Check if DB2 EXIT LIB is updated with currently installed S-TAP
  9. Check if DB2 EXIT LIB is loaded
The script output lists the problems found for each IE, and if you used the fix option, it presents the problem (ERROR), the corrective action taken (ACTION) and the results of the corrective action. The output for a properly configured DB2 IE is DB2 Exit IE in <DB name> has a GOOD setup.

User response: Optional. When you have particular actions that are performed by particular users, use one or more of the ts*Response elements.