The following sql was run directly in the AutoSys database to change the status of all "Open" alarms to "Closed"...
update ujo_alarm set state=45 where state=43;
This change is not reflected in WCC. In the Alerts widget, these alarms still show to have a status of "Open" and never update to "Closed".
Release : 11.3.6/12.x
Component : WORKLOAD CONTROL CENTER
WCC collects new alarms from AutoSys autosys and stores them in the WCC database. However, it does not update existing alarms once they have been collected from AutoSys. When the alarm status is updated in the WCC Monitoring tab or Alerts widget, the alarm data in both the WCC and AutoSys databases get updated automatically. However, if there are direct sql changes made to the alarm data in the AutoSys database, these changes do not get automatically propagated to the WCC alarm data.
WCC displays only alarm data from the WCC database. When direct changes are made to the alarm data in the AutoSys database, these changes will not reflect in WCC.
In order for the alarm status to change in WCC, the alarm data in the WCC database must be updated. If a direct change is made via sql to the alarm data in the AutoSys database, the same change must be made in the WCC database.
Here is an example of the query you would need to run in the WCC database to update all "Open" alarms to "Closed"...
update MON_EVENT set event_status_id=45 where event_status_id=43;
NOTE: Direct changes to AutoSys and/or WCC data via sql is not supported and carries risk to your implementation. It is highly recommended to manage AutoSys and WCC data via the utilities provided within the Application and not via direct sql updates, unless otherwise directed by Broadcom support.