Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Information
This documentation supports the 20.02 version of BMC CMDB.To view an earlier version, select the version from the Product version menu.
Reconciliation Engine jobs that do not finish
At times, the Reconciliation Engine might take several minutes to update the status of your job to Successful or Failed. This might cause you to believe that the job did not finish. In such a case, perform the following procedure to verify that the job is still running and that the Reconciliation Engine did not generate any errors.
To troubleshoot Reconciliation Engine scheduled jobs that did not finish
Check the arerror.log log to determine whether any errors occurred with the BMC Remedy AR System Server or the arrecond.exe process. If the AR System server or the arrecond.exe process stops responding, they are restarted and the status of the Reconciliation Engine job is changed to Aborted. However errors, such as ARERR 93 in the arerror.log log, can point to failures caused by performance or AR System connection issues.
Check the Reconciliation Engine Job log for any information about Reconciliation Engine activities. Verify that the last line of the Reconciliation Engine Job log indicates that an activity was completed.
Check the Reconciliation Engine Job logs for any plug-in errors. For example, an ARERR 8755 The specified plugin does not exist error message might indicate an issue with the BMC Service Impact Manager extensions to the BMC Atrium CMDB.
Success
Tip
The Reconciliation Engine job logs follow the <jobName>_<fileNumber> naming convention, where the job name refers to the name of the job to be executed and the file number indicates the number of files created for the job + 1. If you specified a file size limit, multiple files for a single job run will be created, for example, MergeComputers_1, MergeComputers_2, and so on.
Check the arrecond.log log for errors.
Warning
Note
Changes made to the new job definitions are delayed until the next scheduled Job Definition check interval parameter runs. To load the changes immediately, open and save the job from the UI.
