Troubleshooting
Problem
When rebooting the DB server, the GUARDIUM Database Monitor service doesn't start automatically and it has to be restarted manually
Symptom
- GUARDIUM Database Monitoring service is stopped
- GUARDIUM_TAP service terminates unexpectedly and is automatically restarted by the OS
- GUARDIUM Database Monitoring service stays in stopped status and the Collectors lose contact with the STAP Agent.
[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Guardium Database Activity Monitor","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.2;8.0.1;8.0","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.
Was this topic helpful?
Document Information
Modified date:
16 July 2018
UID
swg21598414