Troubleshooting
Problem
Explanation of how DB-Full alert works and how it generates!
Resolving The Problem
The DB-Full alert is sent by the nanny process which is a Self-Monitoring Utility. With this nanny process- Guardium has implemented an internal self-monitoring demon (always running) service utility on collectors and aggregators that wakes up every 5 minutes and does system scan, checking components for optimal configuration, operational effectiveness, and repairs when necessary.
For example if the database has reached the threshold -->The nanny process awakes after its 5-minute sleep period and performs it's checks and scans resulting in finding the DBFull threshold met. At that point an entry in the MESSAGE table is added. Guard_sender checking the MESSAGE table every minute by default sees the new entry, sends an DBFull alert and clears the entry in the table.
Note: This DBFull alert function is an internal coded system alert. It is impossible to change the timing of these alerts send from the nanny process. If necessary, in order to change the timing from every 5 minutes an RFE request should be opened.
https://www.ibm.com/developerworks/rfe/execute?use_case=changeRequestLanding
Document Location
Worldwide
Historical Number
TS002685809
Was this topic helpful?
Document Information
Modified date:
29 October 2019
UID
ibm11076949