CC 5.2 - Problem Schedule BgJob: ORA-00001: unique constraint

[Former Member]

Hi @all,

we have setup SAP GRC Access Control.

It's running on HP-UX and Oracle DB.

If I want to schedule a bg-job for initial full synchronization of the backend systems, I always get the message:

Failed to schedule background job: ORA-00001: unique constraint (SAPxxxDB.SYS_C006087) violated.

Does somebody nows, which tables are affected for saving bg-jobs?

May I could delete that entrys manually.

Kind Regards

Christian

[Former Member]

Hello Christian,

This is a known issue to GRC.

If you search SAP notes with keyword 'ORA-00001: unique constraint', you will get many SAP notes.

It is not true that you cannot run all the SYNC and BATCH analysis in one go.YOU CAN.

When you select all the Checkboxes with * value for all, inside CC 5.x schedule JOBS one by one. Jobs are scheduled in a sequential manner:

User Sync finishes, only then Role Sync start, then Profile Syn......... and so on. It is Top down approach.

Reason why single jobs are scheduled, is that it become easiar to debug the issue, in case you have multiple connectors.

Now coming to issue. Usually reason for this error is that Post-installation steps are not done.

Check following table, should not be empty

virsa_cc_sapobj

virsa_cc_objtext

virsa_cc_actrule

virsa_cc_prmrule

apart from this copy and paste values from table virsa_cc_config.

also please let me know if you are using JCO connectors, and how many.

do you have ORACLE > 10, yes then have you created BITMAPINDEX on table virsa_cc_prmvl

Also check all the CC configuration parameter, none should be EMPTY. do put default values.

Hope this help.

Regards,

Surpreet Singh Bal

[s_pados]

We also get this error when running the Batch Risk Analysis on RAR 5.3. The user synch was run seperately without errors.

Only the User Analysis run is active for one system. But return the message below:

Error while executing the Job for Object(s) :GBWOUDES:Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-00001: unique constraint (SAPSR3DB.SYS_C005811) violated... (see log for details)

It does that for 30 out of 5600 users. Those 30 users have many roles assigned, but so do have many other users which are processed without errors. When we run the SoD analysis for this user directly then it is run without any issue.

[Former Member]

Hi Christian,

no matter it is brand new installation you`ll keep hitting this problem everytime you try to schedule sync job for more than one attribute (user, role, profile). You have to do it one by one. This is application defect in CC 5.2 and can`t be avoided.

Regards,

Iliya

[Former Member]

Dear All,

We are facing probelem while scheduling the Audit Reports in GRC.

1. Server Node is being re-started after scheduling the Job and Job gets aborted.Please see the below lines for error message.

Thr 20 Mon Dec 8 11:47:21 2008

Thr 20 JLaunchIAbortJava: abort hook is called

Thr 20 **********************************************************************

ERROR => The Java VM aborted unexpectedly.

Please see SAP Note 943602 , section 'Java VM crashes'

for additional information and trouble shooting.

**********************************************************************

Thr 20 SigISetIgnoreAction : SIG_IGN for signal 18

Thr 20 JLaunchCloseProgram: good bye (exitcode = -2)

2.Not able to generate any of the Audit Reports due to Error: Java Virtual Machine Crashed after scheduling the BG Job for User Level / Role Level / Profile Level / Management Reports.

3.This problem am facing even if run one job at a time also server process got re-started.

can any one please provoide a solution for this.

Regards,

Delip

[Former Member]

Hi Delip,

please have a look at this note 1075927

Regards,

Iliya

[achristian17]

Hi Delip,

Put your question in a separate thread. This deviates from the thread and makes difficult to guess question to be answered.

[Former Member]

Dear All,

We are facing probelem while scheduling the Audit Reports in GRC.

1. Server Node is being re-started after scheduling the Job and Job gets aborted.Please see the below lines for error message.

[Thr 20] Mon Dec 8 11:47:21 2008

[Thr 20] JLaunchIAbortJava: abort hook is called

[Thr 20] **********************************************************************

• ERROR => The Java VM aborted unexpectedly.

• Please see SAP Note 943602 , section 'Java VM crashes'

• for additional information and trouble shooting.

**********************************************************************

[Thr 20] SigISetIgnoreAction : SIG_IGN for signal 18

[Thr 20] JLaunchCloseProgram: good bye (exitcode = -2)

2.Not able to generate any of the Audit Reports due to Error: Java Virtual Machine Crashed after scheduling the BG Job for User Level / Role Level / Profile Level / Management Reports.

Regards,

Delip

[Former Member]

Hi,

You can select a single system at a time and also run synchronization for each attributes at a time (user, role and profile).

This might resolve your issue.

I had faced a similar issue and was able to resolve through the above method

regards,

Kapil

[achristian17]

What Kapil said is right, I've faced same issue and by doing individual scheduling this had been resolved. During the scheduling job, update fields on the DB Table level having some issues due to unique key.

This workaround works better.

Regards,

Asok

[Former Member]

Hi @all,

I have done it also in the same way like you mentioned. But it still confuses why there are unique constraints if it is a blank new installation.

Kind Regards

Christian

[Former Member]

Hi there

To my understnading , if a job already exist , may it is periodic job scheduled to run the following week or so

and you try to run the same job immediatley in the back ground the unique contraint error occurs as an entry already exists

and its good practice to run all user , role and profile synch at a time

i am not sure if I was clear enough , but I had this issue before .