戻る
-
タイトル
Duplicate database agent topology affects alarms -
説明
A duplicate database agent topology may cause any of the following scenarios
- An alarm for a database agent are turned off but the alarm continues to fire
- An alarm for a database agent fires when the condition is not met
- An alarm for a database agent does not fire when the condition has been met
-
原因
The database agent referenced two difference instances topology data.
When configuring the alarm the system used the old instance's data id to create the registry entries. This caused the alarm to fire.
-
対策
Delete the topology for the agent (we recommend clearing the agent and agent model data on each agent with this issue individually for performance/timeout reasons)- In the Agent Status page, deactivate the database agents firing the alarms.
- Open Databases | Support Dashboard | Database technical Support
- Switch between the Db types tabs (DB2, Oracle, or SQL Server accordingly)
- Click on Clear Agent data
- Highlight the agent which is firing the alarms
- Click on the Delete button
- Click on Clear Agent Model Data
- Highlight the agent which is firing the alarms
- Click on the Delete button
- Check Databases Dashboard and see if the agent is now there.
- Activate the agent from Agent Status
- The data should reappear shortly and re-associate with the old history.