ActiveDirectory Aggregation Error

[ko111 (Kovaradhan Ganapathy)]

Which IIQ version are you inquiring about?

Version 8.3

Please share any images or screenshots, if relevant.

Share all details related to your problem, including any error messages you may have received.

When ever there is an change in the OU of any AD group, group aggregation getting ended with error “org.hibernate.exception.ConstraintViolationException: could not execute statement” in the production.However when we tested the same scenario in sandbox it’s working fine without any issue.
Any suggestion on the above issue would be appreciated!

[lfmsp (Luís Filipe Milhomem)]

Good day,

Could your provide your Active Directory configuration?

Maybe it happen because the Identity Attribute must be inmutable.

Regards.

[enistri_devo (Emanuele Nistri)]

Hi @ko111,
it means that SP try to write an object with it already exist.

It could possibile those object are lock or corrupted or with a missing foreing key.
Trry to search one(in debug or db), see the situacion and clean it.

[vishal_kejriwal1 (Vishal Kejriwal)]

I would say check the data in database if value column exist in spt_managed_attribute with both old and new value of OU .

[pravin_ranjan (Kumar Ranjan)]

@ko111 pls check this thread,

AD Aggregation Issue: org.hibernate.exception.ConstraintViolationException - Compass (sailpoint.com)

[ko111 (Kovaradhan Ganapathy)]

Hi @pravin_ranjan,
We used to follow the step mentioned in the post shared by you earlier like deleting the group/entitlement causing the issue and re-aggregating, though issue is still re-appearing after sometime, so I’m seeking for any permanent solution so that it won’t reappear.
you suggestion on the same would be helpful.

[ko111 (Kovaradhan Ganapathy)]

Hi @enistri_devo,

We observed that when a group’s OU got update from AD, on next aggregation SP consider this OU updated group as new one instead of updating the existing group in SP.
During this SP trying to create this group as a new object with the same hash value as an existing one which causing this aggregation error.

We do tried to remove those group which causing this aggregation error though it’s working only temporarily. So seeking some other way to get the permanent solution

Your suggestion on same would be appreciated.

[enistri_devo (Emanuele Nistri)]

Hi,

can you try to mark this flag in account aggregation and launch an other one(if ou dont have already marked):

[ko111 (Kovaradhan Ganapathy)]

Yeah it was marked(detect deleted account) from the beginning, though we facing the issue.

[enistri_devo (Emanuele Nistri)]

ok, so try to check the db, make a maintenance cycle on db:

1. Index Defragmentation
2. Log File Maintenance
3. File/Data Compaction
4. Integrity Check

[praful1611 (Praful Patel)]

Hi
I am not a expert yet but trying to guess few root causes that might be worth checking in order to troubleshoot this issue.
Identify table names and constraint names in error message
Check for differences in constraints,indexes, and data types
Ensure that hibernation is consistent
Run SQL diagnostics