Troubleshooting
Problem
Why are Guardium reports displaying SQL Server DB Usernames as DB Administrator?
Cause
The guard_tap.ini configuration parameter KRB_MSSQL_DRIVER_INSTALLED=0. Microsoft SQL Server DB Usernames will not be resolved if this is the case.
Diagnosing The Problem
When a report is generatedfrom Guardium for a scenario where DB Admin adds a new user and then the new user logs in and executes DML Commands. But "DB User name" is still being shown as DB Administrator.
Resolving The Problem
1. Amend the guard_tap.ini configuration file manually to include the following
parameter and value.
KRB_MSSQL_DRIVER_INSTALLED=2
2. Re-start the Windows GUARDIUM_STAP service.
Related Information
[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Guardium Appliances","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.5","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21979686