ems.log : ======== Jan 08 16:03:36:006 [AbstractAlarmService [getAlarms] - 45, ems] NasAlarmDao.getResultList query exception. Attempts: 5 Error: PreparedStatementCallback; bad SQL grammar [select a.*, d.cs_id, m.ci_metric_type, m.ci_id, p.cs_attr_value as primaryipv4address from nas_alarms a WITH(NOLOCK) LEFT JOIN cm_device d WITH(NOLOCK) on a.dev_id = d.dev_id LEFT JOIN cm_configuration_item_metric m WITH(NOLOCK) on a.met_id = m.ci_metric_id LEFT JOIN cm_computer_system_attr p WITH(NOLOCK) on d.cs_id = p.cs_id and p.cs_attr_key = 'PrimaryIPV4Address' where alarm_manager is not null]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'alarm_manager'.
It seems the problem occurs because in your environment the column NAS_ALARMS.alarm_manager does not exist. I consulted the specialists, and that column should be there since ems was first added, back in 8.47. Usually making sure you are on the newer release of NAS and dropping the back end tables to be recreated, should resolve the issue.
Release : 8.51
Component : UIM NAS
1. Make sure you are on latest release of nas. Deactivate the nas probe and the ems probe
2. Drop the nas tables by executing the following queries. One by one. ***
DROP TABLE NAS_VERSION DROP TABLE NAS_ALARMS DROP TABLE NAS_TRANSACTION_SUMMARY DROP TABLE NAS_TRANSACTION_LOG DROP TABLE NAS_NOTES DROP TABLE NAS_ALARM_NOTE DROP TABLE NAS_CS_STATE_MONITOR
3. Start the NAS and the ems probes
4. The NAS_* should be recreated. Confirm the column alarm_manager exist in NAS_ALARMS