[Please insert images here, otherwise delete this section]
Please share any other relevant files that may be required (for example, logs).
this query is running and the task servers are used at max
UPDATE spt_managed_attribute
SET modified = :1,
significant_modified = :2,
ncr_originating_networks = :3
WHERE id = :4
Share all details about your problem, including any error messages you may have received.
Errored out certification has this error message An unexpected error occurred: org.hibernate.exception.LockAcquisitionException: could not execute statement
Hello Surjan. The LockAcquisitionException means IIQ could not acquire a database lock while updating spt_managed_attribute. The 0/0 completions and “No Access Reviews Created” confirm the cert errored out before it could build any review items. The screenshot confirms the error, but does not identify which process was holding the blocking lock.
A couple of things that could help narrow it down:
I would suggest pulling the full nested SQL exception from the IIQ logs and checking your database deadlock or lock-wait report. That will point to the exact blocking transaction.
It would also confirm whether an account or group aggregation was running at the same time as the cert generation, since those tasks can create or update managed attributes.
If certification partitioning is enabled, you could try reducing the number of partitions or temporarily disabling it to lower the concurrent load on the table.
If any custom certification rules are configured (exclusion, entity customization, pre-delegation), it would be good to verify they are not modifying or persisting ManagedAttribute objects.
Once you identify and clear the conflicting process, try retrying the certification during a quieter processing window. If it fails again, the deadlock report from the first run should help narrow it down further.
Hi @SurjanK Can you share more details on how you are launching this certification? Where are you launching this cert? Are you using a standardized cert launch, or are you launching from any other rules? Share that code to better investigate.
@SurjanK I don’t think this should be a recurring issue. For all native IIQ module and tasks, whenever it access any object model, it acquires a lock to avoid modification by other process. It seems when you schedule certification, group aggregation was in progress. IIQ releases the lock quickly and during this window other process will wait. In case it cross the threshold, process with errored out like you are seeing now. It’s a rare occurrence.
So, would recommend you retry it one more time and also try when your refresh and aggregation tasks are not running.. In case it still doesn’t work, please share the complete stack trace for review.
