The sql_response probe clears all alarms at every probe restart.
Every time the probe is restarted, by default, alarms are cleared with a "Clearing alarms at startup" clear message.
Is there a method or key to prevent the probe from automatically clearing all open alarms at every probe restart?
Enhancement consolidated into probe hotfix: DE604627
An enhanced version of the probe is available and attached to this KB.
There is a new key in the raw config of the probe "disable_clear_alarms_on_restart". By default the key is set to no, Configure this to yes and the probe will not clear alarms on restart.
Below are the Hotfix release notes and resolved issues:
Probe : sql_response
Version : 1.81-HF1
Release type : hotfix
Description :
When the probe is restarted, by default all the alarms will be cleared. To avoid this, a new key "disable_clear_alarms_on_restart" has been introduced in 1.81-HF1, when this key is set to yes through raw configure, then the alarms will not be cleared on probe restart.
By default, the query timeout is set to 30 seconds. When the user increases the timeout, the probe still throws a timeout error when the query takes more than 30 seconds. This issue is fixed in this hotfix version.
Steps to apply the patch:
1. Deploy the probe hotfix verion 1.81-HF1 on to the robot.
2. Clean up all the conf_sql_response* files from the temp folder.
Path : C:\Users\Administrator\AppData\Local\Temp\2\util
3. Start configuring the probe.
Fixed defect :
DE563272 : sql_response probe clears the alarms automatically on startup.
DE584486 : Query time out was not functioning as per the updated value.
Related KB: Same build as in: sql_response 1.80 appears to ignore query timeout (broadcom.com)