cancel
Showing results for 
Search instead for 
Did you mean: 

Longer time for user level analysis in RAR

Former Member
0 Kudos

Hi All,

Need your help, why RAR takes longer time for some of the entities to run the job- user level analysis report when compared to other entities which are bigger in volume and connected to the same server.

One of the reasons that i could think of is the role design wherein roles are provided with "*" values.

Please provide your inputs.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

First time batch jobs always take long time.

hope you had set

offline risk analysis to NO

SAP_ALL & SAP_NEW are set as critical profiles and config parameter to ignore them is set to YES

related notes are 723909, 1044173,1044174

JCO connections : Jco pool size as 100 and the timeout settings set to high in msec.

regards,

surpreet

Former Member
0 Kudos

Hi Surpreet,

Thanks for the reply, however this is not the first time job run, also please note that other entities for which we are running the jobs are fine, the report is ready within minutes but for this particular entity its taking 4-5 hours.

Regards

Vani

Former Member
0 Kudos

Ok.

then please be more specific what you meant by 'certain entities'.

also i will request you to schedule all the jobs in small parts

say one job for each sync ... user, role, profile

then when scheduling batch job...

schedule one job per system (make sure not to put value of SYS ID directly and rather select form search help)

this way we can drill down further ...

regards,

Surpree

Former Member
0 Kudos

Hi Vani,

There are many possible reasons for the long running job. For eg: Availablity of the background processes. Incase, if all the threads are active, there might be a delay in the execution of the jobs.

The other reason could be the batch of users. The other jobs that are finishing might have users with a few roles, and the current set might have users with more # of roles, with complete authorizations.

No.of rulesets in which the user/role/profile data should be updated.

Please check the log of the job to identify the possible reasons. As a trial and error, you can limit the batch size and see what is actually causing the problem. Also, ensure that the background processes are free when you are performing this option.

You may refer the document document which speaks about performance optimization of GRC AC:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90aa3190-8386-2b10-c4ba-ced67322e...

Hope this helps!!

Regards,

Raghu

Answers (1)

Answers (1)

Former Member
0 Kudos

thanks