EGRC 8.6.5.x: All Control Analysis Jobs Going To Queued Status, Log Shows "ORA-00001: unique constraint (GRC.GRC_INC_CTRL_2526_PK) violated" Error

(Doc ID 2098549.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Application Access Controls Governor - Version 8.6.5 to 8.6.5 [Release 8]
Information in this document applies to any platform.


On : 8.6.5 version, Application Access Contr. Gov.

In Oracle Application Access Controls Governor (AACG), models and controls define conflicts among duties that can be assigned in a company’s applications, and identify users who have access to those conflicting duties.
AACG can also implement “preventive analysis” — it can evaluate controls as duties are assigned to users of the company’s applications, preventing them from gaining risky access.

All control Analysis job are going in queue.

If no other job is running next job submitted should go in started state.

Error in grc.log:
2015-12-29 11:54:41,319 ERROR [GrcExecutorThread-70] AbstractDaoSpr:537 Error while executing SQL statement.
org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [UPDATE GRC_INC_CTRL_2526 SET LAST_RUN_DATE = (SELECT LAST_RUN_DATE FROM GRC_CTRL_CCM_CONTROL_VL WHERE ID = 2526)]; ORA-00001: unique constraint (GRC.GRC_INC_CTRL_2526_PK) violated
; nested exception is java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (GRC.GRC_INC_CTRL_2526_PK) violated


The issue can be reproduced at will with the following steps:
1. Submit CA job.
2. Check the Job status.

The issue has the following business impact:
Due to this issue, users cannot complete the incident analysis.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms