Environment

All UCMDB Versions

Situation

Sometimes touching does not happen on the UCMDB Server

Cause

When a server has very heavy data-in processing the touch interval should be during a time when the server is not so busy.  It can be seen in the logs by JDBC timeouts, such as this one:

CDM_ROOT_1.CMDB_ID AND #CDM_TMP_OBJID.T_VALUES_INDEX=0); Values: 1628131718554,1626390015723,1629859718554,1626403718554,'DFPOne',false,'Host Connection by <...(47)>'], due to exception: java.sql.SQLTimeoutException: [mercury][SQLServer JDBC Driver]Execution timeout expired.
    at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalPreparedStatementImpl.executeUpdate(CmdbDalPreparedStatementImpl.java:393)
    at com.mercury.topaz.cmdb.server.dal.command.datamodel.impl.CmdbDalUpdateElementsWithClassPropertiesAndNotUpdateTimeComplexCommand.updateElements(CmdbDalUpdateElementsWithClassPropertiesAndNotUpdateTimeComplexCommand.java:124)
    ... 106 more

Caused by: java.sql.SQLTimeoutException: [mercury][SQLServer JDBC Driver]Execution timeout expired.

Resolution

To help alleviate the server load, the touch mechanism on the probe can be started and stopped at a time when the server is not as busy.  In the DataFlowProbe.properties file, the following lines can be modified:

# Defines the time when the touch window starts (HH:MM - 00:00-23:59)
appilog.agent.probe.touchWindowMechanism.startTime=05:00
# Defines the time when the touch window ends (HH:MM - 00:00-23:59)
appilog.agent.probe.touchWindowMechanism.endTime=06:00

This resulted in the touch mechanism updating CIs.

You can also read the full support tip here.