Full Refresh Provisioning Task Running Exceptionally Long – From 6 Hours to 30+ Hours

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

8.3p5

Please share any other relevant files that may be required (for example, logs).

ctm Full Refresh Provisioning.xml (3.0 KB)

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

Hi Community,

We’re facing a performance issue with our “ctm Full Refresh Provisioning” task in SailPoint IdentityIQ (v8.3p5). This task has historically completed in around 6 hours and 30 minutes, but the last two runs have extended to over 30 hours, appearing to get stuck or delayed during execution.

There have been no recent changes to the task configuration, and we are unsure what’s causing this sudden degradation in performance.

I’ve attached the full task definition XML to this post.

Has anyone encountered a similar issue or can suggest what might be causing this? Any insights or troubleshooting recommendations would be appreciated.

Thanks in advance!

2

Hi @KaranGulati25

Please try to get following artifacts:

  1. IdentityIQ Logs.
  2. Application Server Logs catalina.out (if tomcat.)
    Look for
    OutOfMemoryError messages.
    database connection issue.
    get Connector-Specific Logs.
    check JVM health.

take DBA help to check what queries are running, any locks during the task.

1 Like
3

@KaranGulati25 Try to run without provision and synchronize one to see if that works faster ? normally we don’t club with event processing. let us know.

1 Like
4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.