Refresh Identity Task Error

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

IIQ 8.3

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

*Identity Refresh task is failing with the error message “*different object with the same identifier value was already associated with the session : [sailpoint.object.Link#0ad272379a621f20819a7378e9c61cb4]

Below options are enabled for this task:

Refresh only identities marked as needing refresh during aggregation

Do not reset the needing refresh marker after refresh

Exclude identities marked inactive

Refresh identity attributes

Refresh manager status

Synchronize attributes

Refresh logical application links

Enable partitioning

Number of partitions: 4

2 Likes
2

The error is due to the link gets updated twice within the same Hibernate session during the Identity Refresh task.

Can you disable " Refresh logical application links" and try running the refresh and try, still gives you the error. Can you also disable portioning and try ??

3

@sanhitasamaddar2025
Please once go through this.

https://community.sailpoint.com/t5/IdentityIQ-Forum/A-different-object-with-the-same-identifier-value-was-already/m-p/36566

4

This error occurs during Identity Refresh due to duplicate Link objects being loaded in the same Hibernate session, often caused by partitioning with logical application links enabled, so disable partitioning or logical application links, run the task again, and ensure there are no duplicate account links for the identity.

1 Like
5

I tried both, but it did not work. The task failed and the error messages are

Maximum refresh exceptions reached
A different object with the same identifier value was already associated with the session : [sailpoint.object.Link#0ad272379a621f20819a729341b7606d]
Task was terminated by user request
Task was terminated by user request
6

I tried that but the task failed

7

@sanhitasamaddar2025
Can you please check result of below query.

select identity_id from identityiq.spt_link where id=‘0ad272379a621f20819a729341b7606d’;

8

Please verify that there are no duplicate Link records for the identity on which the Identity Refresh task is being triggered.

9

Hi Sumit, sure I will try that. But every time I run the task, I am getting different link ids

10

sorry for delay, Can you run the task again and pull the full logs here?

11

Hi @sanhitasamaddar2025 ,

Are you running refresh task by enabling process events?

12

@sanhitasamaddar2025 Do you have custom workflow/rules associated with identity refresh (like any identity attribute rules, target transformation rules, etc) task options where you are loading identites/links? You might want to review and share it here as well for the team to review. We have seen some times error comes where we are decaching all object using context.decache(). You can change them to use context.decache(object) to decache the specific object.

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

13

How can I verify this?

14

Yes, I need to enable the process events

15

There is no custom workflow/ rules. I am running OOTB refresh task

16

@sanhitasamaddar2025 Identity Refresh task is the OOTB task but if you have process events or identity attribute rules, you might want to check that.

17

can you check at the sailpoint DB level?? i

18

@sanhitasamaddar2025,

I think this would be caused by running the aggregation and, at the same time, the identity refresh. It would be causing these kinds of issues. I would like to know, did you configure a sequence task or an individual identity refresh task? If you schedule the individual one, it will cause this kind of issue. However, to clean up this issue, you can go to the debug, open identity, and it might lock an object there. Remove the lock object and try to run the identity refresh, it would be successfully run. It’s better to use a sequence task to avoid this kind of issue.

Thanks,

PVR