This documentation supports the 9.1.04 version and its patches of BMC Atrium Core. The documentation for version 9.1 to 9.1 Service Pack 3 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Ignoring Multimatched CIs during reconciliation

During the identification process, when multiple CIs from the BMC.ASSET data set match a CI in the source data set, the reconciliation process is unable to assign a reconciliation ID to such multimatched CI in the source data set. As a result, these multimatched CIs remain unidentified in the source data set and are processed in every consequent run of the identify activity. This situation adversely affects reconciliation. The Ignore MultiMatch feature allows you to mark these multimatched CIs so that they can be ignored during the next identify activity.

The IgnoreMultimatchInstances field on the RE:Job form indicates whether a multimatched CI should be ignored in the next Identify Activity run for a Reconciliation Job. The IgnoreMultimatchInstances field takes the following values:

  • Yes — Ignores multimatched CIs in the next identification run
  • No (Default) — Considers multimatched CIs in the next identification run

When the IgnoreMultimatchInstances field is set to Yes, the ReconciliationIdentificationError attribute is modified. This attribute is in the BMC_BaseElement and BMC_BaseRelationship classes. The ReconciliationIdentificationError attribute indicates whether a CI has been multimatched.

The ReconciliationIdentificationError attribute can take the following values:

  • NULL (Default) — Indicates that the CI is not multimatched
  • Multi-Matched — Indicates that the CI is multimatched

If you modify a multimatched CI, an internal CMDB workflow resets the ReconciliationIdentificationError attribute to NULL.

To enable ignore multimatched CIs during reconciliation

This multiple step procedure follows the sequence below:

Making the IgnoreMultimatchInstances field visible 

  1. Log on to BMC Remedy Developer Studio.
  2. Select File > Switch Mode > Base Development.
  3. In the AR System Navigator explorer, expand the list and navigate to All Objects folder.
  4. Double-click Forms to open Filtering Options pane on the right.
  5. Click Filtering Options to expand it.



  6. Search for the RE:Job string in the Display items where field, and press Enter.
  7. In the Name column, locate the RE:Job form, and double-click to open it.
    (If required, you should select the Default Admin view tab to view the IgnoreMultimatchInstances field.)
  8. In the RE:Job form, navigate to the IgnoreMultimatchInstances field. 
    By default, this field is not visible to users.



  9. To make the IgnoreMultimatchInstances field visible, click this field in the Properties pane on the right, navigate to Display and expand the Display attribute.
  10. In the Value column, set the Visible attribute to True.
    • The IgnoreMultimatchInstances field is now made visible.
    • Repeat the steps above to make the Job Name field visble.
  11. Select File > Save All, and close the BMC Remedy Developer Studio.

Clearing the cache in the Remedy Mid Tier Configuration Tool

  1. Start the BMC Remedy Mid Tier Configuration Tool and provide the URL to launch the tool.
    For example, - 
    http://<midTierServer>:<portNumber>/arsys/shared/config/config.jsp
  2. Click Cache Settings, and then click Flush Cache and log out.
  3. Close the browser instance.

Updating your reconciliation jobs to Ignore Multimatched CIs

  1. In a new instance of your web browser, type the following syntax to open the RE:Job form:http://<midTierServer>:<portNumber>/arsys/forms/<arSystemServer>/RE:Job.

  2. In the Job Information page, perform an unqualified search by clicking Search.
    Check that the AR Server Configuration allows unqualified searches.
  3. Scroll to the bottom of the browser to view the list of jobs.
  4. Select the job for which you want to change the IgnoreMultimatchInstances setting.
  5. Change the IgnoreMultimatchInstances value to one of the following settings:
    • Yes — Ignores multimatched CIs in the next identification run
    • No — Considers multimatched CIs in the next identification run
  6. Click Save to save the changes.
  7. (Optional) Repeat steps 4 through 6 for any additional jobs.

Reversing the updates made to the IgnoreMultimatchInstances feature

After you complete making changes to all your reconciliation jobs to ignore multimatched CIs, you should disable the IgnoreMultimatchInstances feature.

  1. Change the IgnoreMultimatchInstances field so that it is not visible.
  2. Change the Job Name field so that it is not visible.
  3. Clear the cache in the Remedy Mid Tier Configuration Tool.
Was this page helpful? Yes No Submitting... Thank you

Comments