Troubleshoot > Troubleshooting and Limitations – Discovery Modules > Troubleshooting and Limitations – Merge Clustered Software

Troubleshooting and Limitations – Merge Clustered Software

This section describes troubleshooting and limitations for Merge Clustered Software Discovery.

Problem: Some duplicate Clustered Software instances occur after users run the Merge Clustered Software job.

Possible Cause: The MSSQL Topology by SQL job incorrectly reports MS Clusters as SQL Server instances. This issue was fixed in UCMDB 10.22 or later by adding a new parameter reconciliation.prefer.crg.container to the setSettingValue JMX method in the UCMDB:service=Settings Services category. By default, this parameter is false. If true, Cluster Resource Group (CRG) is selected as the root_container.

Solution: To solve this problem, do the following:

  1. Go to JMX Console > UCMDB:service=Settings Services > setSettingValue.
  2. In the name field, enter reconciliation.prefer.crg.container.
  3. In the value field, enter true.
  4. Click Invoke.

  5. Clear the Data Flow Probe result cache and rerun the Merge Clustered Software job.