SOI Failure - alarms are no longer synchronized - how to debug database queries send by SOI Manager

Products

• CA Service Operations Insight (SOI)

Issue/Introduction

The alarms were not synchronized in SOI, and after the restart of the whole environment, everything was fine again.

soimgr.log we found the error "Could not synchronize database state with session".

The query has expired, and the synchronization with the DB has been broken.


2020-09-01 09:52:56,663 ERROR [PoolThread-50294: AlarmRepoPool => AlarmRepoTask -4503599651758423] util.JDBCExceptionReporter.logExceptions(78)  - The query has timed out.
2020-09-01 09:52:56,664 ERROR [PoolThread-50294: AlarmRepoPool => AlarmRepoTask -4503599651758423] def.AbstractFlushingEventListener.performExecutions(301)  - Could not synchronize database state with session
org.hibernate.exception.GenericJDBCException: could not insert: [com.aprisma.spectrum.app.alarm.common.AlarmUpdateRecord]

--------------------------------------------------------------------------------

Environment

Release : 4.2, 4.3

Component : Service Operations Insight (SOI) Manager

Resolution

The issue was related to transactions timing out, which most likely was caused by a connectivity issue between SOI and the DB instance.

If you need to check the exact SQL query for that transaction that has failed, then you need to enable the property below.

It will log all the transaction queries that are creating the SOI DB, and it will consume more log space on the Manager side.

\CA\SOI\tomcat\lib\hibernate.cfg.xml

<property name="show_sql">true</property>