cancel
Showing results for 
Search instead for 
Did you mean: 

A.C 5.3 background job failed

Former Member
0 Kudos

Hello Experts,

i have a problem with our A.C 5.3 test system when running jobs in the background .

When trying to start a risk analysis in the background i get the message :

Failed to schedule background job: ORA-00001: unique constraint (SAPSR3DB.SYS_C004609) violated

I didnt find exactly the same problem in this forum or in the Service Marketplace.

I check the Daemon and background job workers , 5 are Idle and 1 is stopped.

When i run the risk analysis in the foreground it is working . Is it maybe the ruleset that needs correction because it has an invalid entry ?

thanks for the help

david

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi David,

Have you tried to restart your instance?

A faster way is is just restart the application sap.com/grc~ccxsysgbear in VA

Visual Administrator >> Server >> Services >> Deploy >> Applications radio button >> sap.com/grc~ccxsysgbear >> Stop Application >> Start Application

Good Luck,

Vit

Former Member
0 Kudos

Hello Vit,

thanks for your tip for how to restart the instance in VA. But i already restarted the server and the problem still exists.

As i remember i had this problem already with sp07. Now in SP08 i thought it would be solved, but apparently not ..

Cheerz,

david

Answers (1)

Answers (1)

Former Member
0 Kudos

Did you uploaded your standard rule sets from the ABAP backend?

check page 44/45 in the GRC AC config guide

nesimi

former_member771067
Active Participant
0 Kudos

Dear David,

As of my understaning, this error is not related to Access control 5.3. This related to the oracle database. This error happens, when an attempt been made to insert a record with a duplicate (unique) key in a particular table at the database(oracle) level. This error will also be generated if an existing record is updated to generate a duplicate (unique) key. So try to get the help of any Oracle Dabase(dba) person to rectify this.

perform either of the two to resolve the issue:

1. Remove the unique restriction.

OR

2. Change the restriction to allow duplicate keys. An index could be changed to be a non-unique index, but remember that the primary key must always be unique.

Hi experts,

Please correct me, if I am answering in the wrong way.

Cheers,

Gurugobinda

Former Member
0 Kudos

Hello Gurugobinda,

thanx for your tip, but a 100% dba doesnt exist to ask. Will ask my supervisor than how to continue on this problem .

Maybe i can find this entry on the application and delete it from there .

cheerz,

david