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:
If the problem persists, contact CA Support.