After upgrading to UIM 9.2, the data_engine probe is not starting, fails with "Max restarts reached" error.
data_engine probe log might show some errors like the following

Aug 20 07:53:53:685 [9340] 1 de: Creating bulk object - table: RN_QOS_DATA_<XXXX> for qos: QOS_POWER_STATE
Aug 20 07:53:53:719 [9340] 0 de: CreateFastLoad - CreateAccessor failed
Aug 20 07:53:53:720 [9340] 0 de: CreateFastLoad - ERROR: Code=0x80040e21 Source=Microsoft OLE DB Provider for SQL Server Description=Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Aug 20 07:53:53:720 [9340] 0 de: CreateFastLoad - CreateAccessor Error [0] = 0
Aug 20 07:53:53:720 [9340] 0 de: CreateFastLoad - CreateAccessor Error [1] = 0
Aug 20 07:53:53:720 [9340] 0 de: CreateFastLoad - CreateAccessor Error [2] = 0
Aug 20 07:53:53:720 [9340] 0 de: CreateFastLoad - CreateAccessor Error [3] = 0
Aug 20 07:53:53:720 [9340] 0 de: CreateFastLoad - CreateAccessor Error [4] = 1
Aug 20 07:53:53:720 [9340] 0 de: CreateFastLoad - CreateAccessor Error [5] = 1
Aug 20 07:53:53:720 [9340] 0 de: QoSInsert::Add_BulkInsertObject - CreateFastLoad failed
Aug 20 07:53:53:720 [9340] 0 de: QoSInsert::InitalizeBulkObjects - failed.  m_definition_map size:

Release : UIM  20.3/ 20.4
Component : data_engine

2 methods are available to resolve the issue.

A-1. Deactivate data_engine probe.
A-2. Run the following SQL query against UIM database.

UPDATE S_QOS_DEFINITION SET TYPE = 1 WHERE QOS_DEF_ID = (SELECT QOS_DEF_ID FROM S_QOS_DEFINITION where name='QOS_POWER_STATE');

A-3. Activate data_engine probe.

B. Apply data_engine 9.20 HF2. It is available in UIM hotfix index page.

https://techdocs.broadcom.com/us/product-content/recommended-reading/technical-document-index/ca-unified-infrastructure-management-hotfix-index.html?r=2

Experienced this same  behavior with Exact log entries , during an upgrade from UIM 9.0.2 to  20.3

Applied the above remedy but configured setting did not take because restarts set entry back to default value of 0 from the recommended value of 1

in the data_engine/ scripts/sqlserver_update_qos_type

 FROM S_QOS_DEFINITION where name='QOS_POWER_STATE';

We made configuration change to the setting:

SET @lsql = N'UPDATE S_QOS_DEFINITION SET TYPE = 1 WHERE QOS_DEF_ID = '+CAST(@lQosDefID AS NVARCHAR(10));

from 0  to keep change permanent.

Issue was resolved