mon_config_service Fails to Start After Upgrading to CA UIM v8.4
search cancel

mon_config_service Fails to Start After Upgrading to CA UIM v8.4


Article ID: 37675


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


When a user upgrades to CA UIM v8.4, there could be contention for accessing database schema between UIM processes. This could prevent the mon_config_service probe from correctly creating its own database objects. If this happens, mon_config_service generates an mcs_fatal.log file and fails to start. This behavior has been observed sporadically with Oracle databases, but could potentially occur with Microsoft SQL Server or MySQL databases.

Note: The information included in this article is applicable only during the initial upgrade to CA UIM v8.4.  If you perform this procedure after a successful upgrade and using Monitoring Configuration Service (MCS) to create configuration profiles, the database is wiped clean.

To recover from this scenario, complete the following steps:

1. Deactivate the mon_config_service probe.
2. Run the SSR2_drop_all_tables.sql script to drop the MCS database schema. The script is located in the following directory:
3. Activate the mon_config_service probe. When the probe activates, the MCS schema is rebuilt.
4. Deploy the mon_config_service_templates package from the Web Archive to the Local Archive. This inserts the MCS templates into the database.

If the problem persists, contact CA Support.


Release: CNMSPP99000-8.4-Unified Infrastructure Mgmt-Server Pack-- On Prem