No alarms in the OC alarm console after upgrade to CU3.

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Alarms were displayed in the IM alarm sub console but no alarms were displaying in the OC alarm console. Har file showed errors from getAlarms calls displaying Internal Server 500 errors. In the OC the message displayed was-> Data Access Error

EMS log error:

2025-07-08 07:11:52.957 [AlarmCacheUpdateThread]  ERROR com.ca.alarmservice.dao.ems.EmsAlarmDao:getAlarms:58 ems.EmsAlarmDao - Unable to retrieve alarms from EMS.
com.nimsoft.nimbus.NimException: java.lang.RuntimeException: (120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'dispatcher'
Caused by: java.lang.RuntimeException: (120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'dispatcher'

Environment

• The issue of no alarms in the OC console started right after upgrading from CU2 to CU3 (not CU4). The issue was seen again even after upgrading the nas to 23.4.4.1 as the OC alarm console issue with no alarms persisted. OC displayed the Data Access Error.
• DX UIM 23.4.3
• ​nas 23.4.3, or 23.4.4.1

Resolution

Steps taken:

1. Deactivated ems
   
   
2. Deleted the ems db folder
   
   
3. Activated ems and checked log and found no further errors
   
   
4. Checked wasp, nas, operator console and controller logs - all clear
   
   
5. Redeployed wasp_alarmviewer_api but no change
   
   
6. Finally, the issue didn't seem related to the versions of nas 23.4.3.2 and/or 23.4.4.1 as we analyzed and resolved all potentially related probe issues/errors seen in ANY of the probe logs. None of the probe logs showed evidence of a problem at that point.
   
   
7. Therefore, I recommended reinstall of the OC version 23.4.3 and it resolved the OC alarm console no alarms issue, and nas 23.4.3 was working just fine.