cancel
Showing results for 
Search instead for 
Did you mean: 

Getting " Error creating request " when creating request in CUP

Former Member
0 Kudos

Hello every one,

We are getting error " Error creating request " while creating the CUP request.Find below latest system-log and help me to resolve this issue.This is urgently required please help us.We checked our workflows and all the connections every thing is fine but we are getting this error when creating request.

Our system is GRC-5.3 Sp-5

Praveen

2011-09-16 13:44:35,587 [SAPEngine_Application_Thread[impl:3]_9] ERROR BO Exception in Save request

com.virsa.ae.core.BOException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00146299) violated

at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:438)

at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:262)

at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:89)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)

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(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Caused by: com.virsa.ae.dao.DAOException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00146299) violated

at com.virsa.ae.dao.sqlj.RequestDataApplicationsDAO.insert(RequestDataApplicationsDAO.sqlj:160)

at com.virsa.ae.accessrequests.bo.RequestBO.saveApplications(RequestBO.java:1756)

at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:378)

... 19 more

Caused by: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00146299) 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.RequestDataApplicationsDAO.insert(RequestDataApplicationsDAO.sqlj:148)

... 21 more

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

this looks like you have a problem when saving the request at the database level.

1.Review the number ranges in CUP configuration.

If you deleted data directly from the GRC tables, you need to review if you covered all the relevant tables

Kind regards,

Nuno Jesus

Former Member
0 Kudos

Hi Nuno,

We created new number range still it is giving same error.Can you specify the table names where this request number stores.

praveen

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Rizwan,

The tables related to CUP are VIRSA_AE*, like Anil mentioned, but there are others.

You should check with your DB Admin all the tables and what's the tables content.

Changing the data at a table level is a critical operation and should only be performed by SAP, or following SAP direct instructions.

If you could clarify what you are trying to do, it may help us to better understand.

Is this a cloning activity or a fresh installation?

Did you delete any data from the tables?

Regards,

N

Former Member
0 Kudos

Hi,

Do the following checks:

1. Ensure that the GRC RAR connectivity is perfect (check the connector, user ID and password), if risk analysis is enabled.

2. Ensure that the number range is properly defined. May be try to setup a new number range.

3. Ensure that the initiators, stages, and paths are properly defined. Check that all the approvers, administrators are active in the system.

4. Check if the other request options are working fine.

Also, you are on a very old SP. Try to upgrade to the latest SP available, which has lots of fixes.

Regards,

Raghu

Former Member
0 Kudos

Hi Raghu,

We checked all the connections and workflows are correct.We changed the number range and checked still it is not allowing to create request.

praveen

former_member325725
Participant
0 Kudos

Hi Praveen,

The issue could be because of an inconsistency in the associated DB tables. Pls check to identify the table that complaints about the constraint violation. In general, the I've found that the log reports violation related to an index and with a DB/Basis Admin's help, you could identify the table that has the inconsistency. The fix to the issue lies in correcting this entry either by a deletion of the record or even a truncation of the table itself. I would suggest you take the advice from SAP esp. if the issue happens in a prod system.

You can refer to the Note: Note 1591058 - sql.DuplicateKeyException: ORA-00001: Unique Constraint.. which will help you in understanding the options you got to fix the issue, though the table causing the issue in your case could be different.

Regards, Anil

former_member325725
Participant
0 Kudos

Further Info: The affected table is : VIRSA_AE_WF_RQNTFC

Hope this helps,

Regards,Anil