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 aborted jobs due to insufficient memory
If your computer does not have enough memory space, your reconciliation jobs might abort. For more information about the software and hardware requirements for BMC Atrium Core, see the BMC Atrium Core installation information.
To troubleshoot jobs aborted due to insufficient memory
Check the arerror.log file to determine whether problems with the BMC Remedy AR System server or arrecond executable occurred. For more information about the arerror.log file, see AR System server logging.
Monitor the amount of memory available on your computer and check the processes that are consuming large amounts of memory.
Add more disk space to the server TEMP disk or redirect TEMP to another disk that has more disk space.
Examine arrecond.log and the Reconciliation Engine job log files to determine the operation that the Reconciliation Engine was performing when the insufficient memory error was generated. For more information about Reconciliation Engine logs, see Analyzing-Reconciliation-job-logs.
Make sure that the server has enough resources, such as virtual memory and space for BMC Atrium CMDB tasks. Due to intensive data manipulation, the Reconciliation Engine might need to use more virtual memory than available.
If the reconciliation job uses the Copy activity, make sure that Copy Relationship field is set to By Qualifier to avoid insufficient memory issues.
