Self Monitoring Initialization Error

book

Article ID: 195408

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

I'm building a new Prod system.  I started the MQ server and then the application server.  The Triage test show it has completed.  However, in the debug log file I see the following message about once a minute.  Can you please let me know if there is a procedure to fix the problem?  (the log files will be uploaded to the case)

Self Monitoring Initialization Error 
java.lang.NullPointerException

Cause

Alert generated by the Universal Connector were stuck in the DB. They were active but not impacting the CI on the SOI console.

Environment

Release : 4.2

Component : Service Operations Insight (SOI) Manager

Resolution

- There were multiple active alerts on self monitoring CI generated by the Universal Connector (source CA:09997_*) in the past and SOI manager failed to make these alert inactive when the connector's were running normal. These alerts were stuck in the SOI DB and in SOI console they were not impacting the 'CA Service Operations Insight' CI and its parent service.

To resolve the issue ran the following SQL queries

Note: The connectorid 5 is the default for the Universal connector. It may differ from what you have. The best thing to do is to run "select * from ConnectorConfiguration" SQL query and find the connectorid for the Universal connector has in your SOI DB.

- Please back up the SOI DB before running the following queries

delete from alerts where connectorid=5
delete from alerthistory where alertid not in (select alertid from alerts)
delete from alerthistory where alertid in (select alertid from alerts where connectorid=5)
delete from alertimpact where alertid in (select alertid from alerts where connectorid=5)