cancel
Showing results for 
Search instead for 
Did you mean: 

GRC 5.3 - CUP - SAPSR3DB.SYS_C006582

Former Member
0 Kudos

Hi all,

I'm tring to understand the reason why, after SP application to GRC-SAC-SAE 5.3_19.16, existing Roles are no more editable and no new roles can be created/uploaded.

In CUP error log is reported:

Caused by:

com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C006582) violated

I've read that brobably exist a lock on DB tables.

Any suggestion will be appreciated!

Best regards

Claudio

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Claudio,

Please, check the following SAP notes:

1873924

1591058

Let me know if you can solve the issue.

Thank you,

Fernando

Former Member
0 Kudos

Hi Fernano,

Notes will not solve this strange issue, as I can create and approve and provision CUP new requests.

The second not is out of scope, it doesn't refere to CUP.

Thanks,

Claudio

Former Member
0 Kudos

Hello Claudio,

Please, let us know the table which the constraint is referring to. Can you check in CUP logs or attach error logs here?

Thank you,

Fernando

Former Member
0 Kudos

Hi Fernando,

This error is generated tring to change the Risk level or Business Process or others for a Role already in CUP.

2014-02-28 10:20:59,982 [SAPEngine_Application_Thread[impl:3]_31] ERROR Error in Saving roles
com.virsa.ae.core.BOException: com.virsa.ae.dao.DAOException: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C006582) violated

at com.virsa.ae.configuration.bo.ChangeLogBO.logChange(ChangeLogBO.java:67)
at com.virsa.ae.configuration.bo.RoleDetailsBO.logChange(RoleDetailsBO.java:534)
at com.virsa.ae.configuration.bo.RoleDetailsBO.saveRoleDetails(RoleDetailsBO.java:309)
at com.virsa.ae.configuration.actions.AdminSaveRoleAction.saveRoleDetails(AdminSaveRoleAction.java:521)
at com.virsa.ae.configuration.actions.AdminSaveRoleAction.execute(AdminSaveRoleAction.java:65)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by:
com.virsa.ae.dao.DAOException: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C006582) violated

at com.virsa.ae.dao.sqlj.ChangeLogDAO.insertChangeLog(ChangeLogDAO.sqlj:73)
at com.virsa.ae.configuration.bo.ChangeLogBO.logChange(ChangeLogBO.java:54)
... 21 more
Caused by:
com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C006582) violated

at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:259)
at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.executeUpdate(RTStatementJDBCPrepared.java:267)
at sqlj.runtime.ExecutionContext$StatementFrame.executeUpdate(ExecutionContext.java:1124)
at sqlj.runtime.ExecutionContext.executeUpdate(ExecutionContext.java:718)
at com.virsa.ae.dao.sqlj.ChangeLogDAO.insertChangeLog(ChangeLogDAO.sqlj:59)
... 22 more

Regards,

Claudio

Former Member
0 Kudos

what is your backend system version details?

May be there would be this compatibility issue with the upgraded SP level for GRC.

Thanks,

Ameet

Former Member
0 Kudos

Hi Ameet,

Your question could be right.

Please take care that I incurr in the issue not only in importing role from Backend (so VIRSANH could be involved) but creatin a new role directly on CUP, or modifing a role alredy present on CUP.

Let me know you idea.

Regards,

Claudio

Former Member
0 Kudos

Hi Claudio,

Your GRC and Backend system version details..?

I am assuming you are on SP 16 for GRC-component and SP 19 but not sure of the backend version.

Please refer to: http://service.sap.com/sap/support/notes/1352498 It might be because of compatibility issues.

Thanks,

Ameet

Former Member
0 Kudos

Hi Ameet,

Our backend is:

VIRSAHR 530_700 0017

VIRSANH 530_700 0019

GRC-CUP is: SP19

Claudio