After upgrading SOI to SO15850 / CU1 / Tomcat 7.0.107, there are a lot of the following entries in the service-discovery_IFW.log:
servicediscovery.ServiceDiscovery - Service discovery error..
org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [
...
]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Could not continue scan with NOLOCK due to data movement.
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Could not continue scan with NOLOCK due to data movement.
Release : 4.2
Component : SOI ALERT MANAGEMENT
No cause could be found and the error did not persist but it does indicate a problem with the database
There is an article here which investigates the problem in more detail in general with MS SQL Server
https://www.sqlshack.com/fixing-error-601-could-not-continue-scan-with-nolock-due-to-data-movement/
Specifically for SOI, the soitoolbox has options to check for any concerns with the database: