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

book

Article ID: 199452

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

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

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

We have looked at the logs - the lines are attached below.
As described the query has expired and the synchronization with 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

Component : Service Operations Insight (SOI) Manager

Resolution

There was some transactions timed out issue .

There might be some connectivity issue between SOI and DB instance.

If you need to check exact sql query for that transaction which has failed then you need to enable below property.

But it will logged all the transactions query which is creating with SOI DB and it will consume more log space on Manager side.

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

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