Full Sync User Analysis job errors out after running for more than 48 hours

[Former Member]

Hi,

We have just installed GRC 5.3 and configured RAR. User, Role, Profile Synchronization jobs completed successfully. Full Sync User Analysis job is failing repeatedly after running for more than 48 hours.

1.'Action' level job completed successfully.

2.'Permission level' job is failing for certain users. On further analysis, we found that users assigned to Developer and functional roles, errors out after running for 45 -50 minutes for each of those users. Users assigned to Configuration role, Basis and Security completes.

On reading some of the answers regarding performance issues, our DBA created an index for one of the tables. This did not help.

Job log for errored users is as follows.

[ibm][db2][jcc][102][10040] Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.

Use getNextException() to retrieve the exceptions for specific batched elements.com.virsa.cc.xsys.riskanalysis.AnalysisEngine.insertPRMVL(AnalysisEngine.java(Compiled Code))

com.virsa.cc.xsys.riskanalysis.AnalysisEngine.outputPermissionViolation(AnalysisEngine.java(Compiled Code))

com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java(Compiled Code))

com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:312)

com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1047)

com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1331)

com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:405)

com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:267)

com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:249)

com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)

com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)

com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)

com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)

com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)

com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)

com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)

com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)

com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

java.security.AccessController.doPrivileged1(Native Method)

java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))

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

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

Looking for assistance from the experts.

Regards

Ram Mopuri

[Former Member]

Hi,

In the Configuration tab (Additional Options), do you have "Enable Offline Risk Analysis" set to "Yes"?

If yes, the error could occur because of updating the conflict permission details in the offline table VIRSA_CC_PRMVL. I believe this will occur in users who are assigned to big roles that contain lots of authorizations.

As a test workaround, if you had set "Ignore Critical Roles & Profiles" to yes, you can enter those big roles into the list and run the batch risk analysis for only those users with errors.

As another test workaround, If you had set "Consider Org Rules" to yes, set it to "No". After that, run again batch risk analysis for the users with errors.

I agree it is not a direct solution to the problem (which I am also facing right now and dealing with SAP) but helps to identify where the problem is.