Stucked Modify Core Task Processing a Deleted MSKEY

[santiobejero]

Hi Guys,

We are having a serious Production Problem right now, the Modify Core Task is looping in and running indefinitely processing a specific MSKEY in which was deleted already. Below is the last MXP_PROV audit of the specific job for the specific MSKEY:

MSKEY=800296

ACTIONID=1819

STATE=2

PARENTID=751

TASKTYPE=0

ACTIONTYPE=0

RETRYCOUNT=1

WAITCOUNT=0

PREVSTATE= EXECTIME=10/5/2016 3:38:35 PM

UPDTIME=10/5/2016 3:38:35 PM REPOSITORYID=

AUDITREF=14874998

LINKAUDIT=

MSG=

DEPPRIV=

PROCESSINFO=

=============

Below is the MXP_AUDIT last entry:

AUDITID=14875054

TASKID=3542

MSKEY=800296

AUDITROOT=

POSTEDBY=MXMCIDP_ADMIN

POSTEDDATE=10/5/2016 4:06:40 PM

STATUSDATE=

PROVSTATUS=4

LASTACTION=

REFAUDIT=

MSG=

REPOSITORY=

USERID=

IDSID=1

STARTEDBY=

I want to ask on below solutions I am thinking if any of this you think will work.

1. Delete the provisioning queue for that specific MSKEY.

2. Manually update the status of the task by doing an SQL Update command.

3. I have checked the scripts and saw that the reason for failure is because the TASKEXECUTE = NULL, I am thinking what if I remove temporarily that specific criteria in th script (I will copy the script, remove that criteria and add taht script on the TASK MODIFY Temporarily). What might be the implications.

If you have any other proposed solutions, it is highly appreciated at this point. We are now in the decision of raising an OSS but in parallel if someone can help us will be appreciated.

Thanks in advance!

KR,

Santi

[Steffi_Warnecke]

Hello Santi,

could you please add on which version you are? 7.2 SP? 8.0? You can also add it as a user tag. Thank you. 🙂

.

I had some looping when updating an ldap account. It helped to change another field in the UI and thus trigger another update to the backend. Then the loop was broken. But nothing with deleted content yet, sorry.

.

Regards,

Steffi.

[santiobejero]

Hello Steffi,

I forgot to add the details, here they are:

1. IDM Version: 7.2

2. SP Level: SP10

I will take note of adding it on tags for my future engagements here. 🙂 Hope you can help me identify the root cause of this.

[santiobejero · Accepted solution]

Hi All,

We already finished the activity after carefully planning the deletion. As per SAP Message, we need to delete the orphaned mskey so the task will avoid looping. After deleting, the task is running and all of our modify changes are now flowing appropriately in Production. Thanks.

Best Regards,

Santi