cancel
Showing results for 
Search instead for 
Did you mean: 

Error During Risk Analysis in ERM

Former Member
0 Kudos

Hi Friends,

When I am creating a role in ERM in the step 'risk analysis' I am getting stuck. When I am clicking in 'GO' it is sayning system doesn't exist in RAR. But when I am clicking it in Simulate it is sayinng background job scheduled and gone through the step and i can proceed from the approval step.

Please suggest if somwhere I am going wrong.

Thanks & Regards,

Satyabrat

Edited by: Satyabrat Mohanty on Nov 5, 2009 3:54 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Satyabrat,

The system/connector name in ERM and RAR should match up for the risk analysis to work. ERM isscheduling the background job and lets you move forward in the process. If you look at the logs, even this background job should be failing due to this error.

Alpesh

Former Member
0 Kudos

Hi Alpesh,

Thanks for your response. I have created system/connector with the same name in ERM and RAR (old one still exists). When I am running the risk analysis in ERM by selecting the new system, It is giving error 'Action Failed'.

FYI,

I have deactivated the old ADAPTER and also remove old system assignment from the landscape and assigned the new one.

Please suggest.

Thanks & Regards,

Satyabrat

Edited by: Satyabrat Mohanty on Nov 8, 2009 5:03 PM

Edited by: Satyabrat Mohanty on Nov 8, 2009 5:06 PM

Edited by: Satyabrat Mohanty on Nov 8, 2009 5:07 PM

Former Member
0 Kudos

Please find the error details

Please find the error details below

2009-11-08 14:30:00,749 [SAPEngine_Application_Thread[impl:3]_13] ERROR java.lang.NullPointerException

java.lang.Throwable: java.lang.NullPointerException

at com.virsa.re.bo.impl.RiskAnalysisBO.getTransactionsFromSTCODE(RiskAnalysisBO.java:842)

at com.virsa.re.bo.impl.RiskAnalysisBO.performTranLvlRiskAnalysis(RiskAnalysisBO.java:443)

at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:173)

at com.virsa.re.role.actions.RiskAnalysisAction.performAndShowRiskAnalysis(RiskAnalysisAction.java:1430)

at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:103)

at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:270)

at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)

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

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)

at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)

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

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:102)

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

Thanks,

Satyabrat

Former Member
0 Kudos

I have some questions...does you RAR work correctly? Can you do the same simulation in RAR and see you get some results or not? Have you run all the necessary initial background job (e.g. tcode sync, object sync etc.) in ERM?

Alpesh

Former Member
0 Kudos

Hi Alpesh,

I have reconfigured the whole RAR again and now it seems to be working fine.

But in the informer tab under Management View--> Risk Violations it is showing the total no of user analyzed but no violations it is showing '0'. Can you please tell me how to get the violations list, from where it reads the violations

Thanks,

Satyabrat

Former Member
0 Kudos

You need to make sure that your rules are configured correctly and run the full sync role/user sync, full user/role anaylsys job and management reports to see the violations count.

Alpesh

Former Member
0 Kudos

Hi Alpesh,

I have uploaded the rule set availabale with the S/W and shedule the two background jobs

Where 1st job 'user/role/profile full synchronization' completed success fully the 2nd job 'user/role/profile full analysis & management reports' is in status running and it is more thatn 24hrs.

Recently I have cancel the job.

Please advice if it is OK or some where something is wrong.

Kind Regards,

Satyabrat

Former Member
0 Kudos

You can not cancel the job. It can run for more than 24 hours very first time depending on the amount of data. That is the job which displays the violation count so please rerun it.

Alpesh

Former Member
0 Kudos

Hi Alpesh,

I have reshedule the job, but it finished with error, I found that one of my table space got filled, then I extended the table space and again reschedule it but again the table space got filled and when I am checking the log some of the analysis are in error status, how to proceed with that now , it's swallowing the table space.

Thanks & Regards,

Satyabrat

Edited by: Satyabrat Mohanty on Nov 16, 2009 10:48 AM

Former Member
0 Kudos

Clean up all the alanlysis tables by opening a CSS message with SAP. Keep enough space on the server by following SAP GRc Access Control sizing guide and run the background job.

Alpesh

Former Member
0 Kudos

Hi

I have raised a message to SAP to delete connector as well as all the data related to it but they are saying they are not providing any scripts to delete the data any more. can you please help me in this regard.

Thanks & Regards,

Satyabrat