After re-enabling the database agent alarm and saving the change all subjects for the email notifications were corrupted in Settings | Administration | Alarms. In the notification the subject only contained the -2147483648. Saving alarm changes may be also noticeably slower.
To help identify the issue, generate a FMS Support Bundle and open the bundle file:
MonitoringPolicies_<date>_<time>.xml
Under registry-variables search for the string "-2147483648"
Example:
<Topology-object-registry-value default-value="java.lang.String;-2147483648
@@PS@@Warning@@PS@@lowSeverity@@SS@@@@SS@@@@ES@@@@ES@@@@ES@@@@PS
@@mediumSeverity@@SS@@zzdba
@mycompany.com@@ES@@dba2@mycompany.com@@ES@@@Severity@ alarm for @DBType@ instance @InstanceName@ on host @Hostname@ was generated: @AlarmMessage@@@ES@@@@PS@@highSeverity@@SS@@@@SS@@@@ES@@@@ES@@@
@ES@@@@PS@@" id="8a2ab8d34505d86a01459010d988403e" is-user-created="true" variable-name="DBSS-WorkerThread_NotificationSettings" object-unique-id="13f965f3-cf98-4a3c-a687-49ec365140b7">
When making a change to a group of agents in the Alarms are of Global Administration, if the blue inconsistent values arrow is seen when editing the email configuration settings, the change should be reapplied to all of the agents selected before saving changes.
For example, if you select a group of nine agents, make a change to the configuration and save it, then later access ten agents and the display shows inconsistent values, then the change needs to be reapplied to all of the database agents again.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center