Acces History task takes always +- 2h and does not speed up

[Remold (Remold Krol)]

Which IIQ version are you inquiring about?

8.4p2

Please share any images or screenshots, if relevant.

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

No special logging, using default configuration.

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

Access History taks 2 hours to complete, independent of we run it weekly or daily.
All subtasks complete quite fast except the `Data Extract processor for role, account and identity.
Total object to be processed is 13,000
Even during the weekends and running the task every day it still runs 2 hours while the activity/usage of IIQ during the weekend is very very low (almost none).

We are using the standard configuration as described on Setting Up Access History Task

Our IIQ environment is almost 9 years old started with version 6.3 and has been upgraded to 8.4p. The last upgraded was from 8.3p4 to 8.4p2 (via 8.4) and we did not start 8.4 during the upgrade process.

As per my understanding the ‘Access History’-task will only process the newest changes after the first run of this task.

– Remold

[paul_hilchey]

@Remold, in the debug page, look for objects of type NamedTimestamp. There should be one named “Dispatch Access History”. The timestamp attribute in it should be updated when the Dispatch Access History task completes. If it’s not being updated for some reason, then objects will be processed again and again.

[Remold (Remold Krol)]

We have an updated Dispatch Access History Object.

The timestamp in this object is the last time we started the ‘Access History’-task.

The last task result:

– Remold

[paul_hilchey]

@Remold, what types of objects are being extracted?
I’ve seen that managed attributes get updated everytime they are aggregated, and then processed by Dispatch Access History.

You do seem to have a lot of deletion objects, though.