This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Atrium Core - CMDB
AtriumCore Reconciliation Engine 8 and 9
Reconciliation Groups or jobs are separated into two types. Standard or Custom.
This is not exclusively documented, but it is useful to know that:
a. Jobs that are associated with standard rules set can not have their rules modified.
b. Jobs that are custom and not associated with standard rules set can only be modified from inside that job.
You may see that saving job specific rules give you access to the consoles that make the changes, but the changes will not be saved or take effect unless you uncheck the "Use standard rules for participating datasets" option.
You may see that saving a change to Standard Rules takes a while and the console sits there with an hour glass while the changes are going on in the backend.
It will eventually complete so please be patient. Rules are being written to backend form called (RE:Group) where the regeneration of standard rules are done.
The more records you have in that form the longer will saving the job rules take.
Rushed interaction with the RE console can lead to errors later on. For example:
DEBUG http-bio-80-exec-12 com.bmc.re.util.REUtil - Exception in createREGroup:ERROR (552): The SQL database operation failed.; Cannot insert duplicate key row in object 'dbo.T814' with unique index 'I814_301067400_1'.
The duplicate key value is (Atrium Explorer - Identification and Merge - Identification Group - BMC Atrium Explorer - BMC_TapeDrive, BMC.CORE, 2).
In this example the "814" schemaId is assigned to RE:Group in ARSchema. This form stores all of the reconciliation group types including identification, qualification and merge activities.
The error then means that the index named "I814_301067400_1" has "RE Group Name", "NameSpace" and "Group Type" as part of Unique index.
Please don't remove the index. Instead remove the duplicate record from RE:Group table. Adding or deleting the standard rules triggers restructuring of RE rules. Existing records are deleted and new records are created.
Due to this unique index the operation failed in this example.
You may need to query the table directly at the database level to see all groups. AtriumCore UI of any type is only set to show valid rules from the set. In some cases the "Unknown" or invalid group can only be seen using a SQL query.
SQL: "select RE_Group_Name,RE_Group_Type from RE_Group group by Re_Group_Name,RE_Group_Type having COUNT(Re_Group_Name) > 1"
It should return no results.
You can also try running a query that looks for invalid group types. There should be only 3 types:
0 - Precedence group
1 - Qualification group
2 - Identification group
Any group outside of this range is invalid and will likely not show up in AR User Tool or AR Midtier form.
Delete it and restart ARRECOND engine.