on 09-21-2009 3:46 PM
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you uploaded your standard rule sets from the ABAP backend?
check page 44/45 in the GRC AC config guide
nesimi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.