GRC ERM not running a risk anlaysis

[Former Member]

Hey,

I'm having some trouble getting ERM to run a risk analysis... RAR and ERM are sitting on the same server. However, I still have a user ID with RAR and ERM admin rights,, but ERM is not communicating properly with RAR. ERM is also not showing an error in the job log.I keep attempting to get ERM to run a risk analysis, but it seems like its running in a loop. Has anyone else ran into this issue? Here is the log.

2010-11-15 00:04:49,494 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:04:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:04:49,494 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:04:49,494 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:04:49,494 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:04:49,494 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:04:00.0

2010-11-15 00:04:49,494 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:04:49,494 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:04:49,494 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:04:49,494 [Thread-98] DEBUG Thread interruptedfalse

2010-11-15 00:05:49,508 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:05:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:05:49,508 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:05:49,508 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:05:49,508 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:05:49,508 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:05:00.0

2010-11-15 00:05:49,508 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:05:49,508 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:05:49,508 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:05:49,508 [Thread-98] DEBUG Thread interruptedfalse

2010-11-15 00:06:49,523 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:06:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:06:49,523 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:06:49,523 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:06:49,523 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:06:49,523 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:06:00.0

2010-11-15 00:06:49,523 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:06:49,523 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:06:49,523 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:06:49,523 [Thread-98] DEBUG Thread interruptedfalse

2010-11-15 00:07:49,537 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:07:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:07:49,537 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:07:49,537 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:07:49,537 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:07:49,537 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:07:00.0

2010-11-15 00:07:49,537 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:07:49,537 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:07:49,537 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:07:49,537 [Thread-98] DEBUG Thread interruptedfalse

2010-11-15 00:08:49,552 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:08:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:08:49,552 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:08:49,552 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:08:49,552 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:08:49,552 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:08:00.0

2010-11-15 00:08:49,552 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:08:49,552 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:08:49,552 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:08:49,552 [Thread-98] DEBUG Thread interruptedfalse

2010-11-15 00:09:49,566 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:09:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:09:49,566 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:09:49,566 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:09:49,566 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:09:49,566 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:09:00.0

2010-11-15 00:09:49,566 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:09:49,566 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:09:49,566 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:09:49,566 [Thread-98] DEBUG Thread interruptedfalse

2010-11-15 00:10:49,581 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:10:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:10:49,581 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:10:49,581 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:10:49,581 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:10:49,581 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:10:00.0

2010-11-15 00:10:49,581 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:10:49,581 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:10:49,581 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:10:49,581 [Thread-98] DEBUG Thread interruptedfalse

2010-11-15 00:11:49,595 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:11:49 CST 2010 - Running BackgroundJobScheduler #@#@#@#

2010-11-15 00:11:49,595 [Thread-98] DEBUG Name of scheduler is 7892352

2010-11-15 00:11:49,595 [Thread-98] DEBUG Number of schedular Threads ========== 3

2010-11-15 00:11:49,595 [Thread-98] DEBUG getJobsTobeScheduled query ====== SELECT A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC FROM VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C WHERE A.TASK_ID = B.TASK_ID AND A.STATUS_ID = C.STATUS_ID AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y') AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting') AND A.NEXT_IN_DATE <= ? AND B.LNGID = 1 ORDER BY JOBID

2010-11-15 00:11:49,595 [Thread-98] DEBUG scheduler is checking NextInDate with 2010-11-15 00:11:00.0

2010-11-15 00:11:49,595 [Thread-98] DEBUG Jobs list Size ==== 0

2010-11-15 00:11:49,595 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]

2010-11-15 00:11:49,595 [Thread-98] DEBUG Thread Name===== Thread-98

2010-11-15 00:11:49,595 [Thread-98] DEBUG Thread interruptedfalse

[Former Member]

Hey all,

Thanks for all your help. I was able to resolve this issue by following a few steps.

First off, we were having performance issues with RAR, and had been unable to get a Full Batch Risk Analysis to complete without any errors. I believe that this was the main culprit in our ERM Risk Analysis issue.

We were able to resolve this problem by upgrading from AC 5.1 to AC 5.3, increasing the amount of memory on the server, and increasing all of our performance settings way beyond SAP's recommended values, which are outlined in SAP note 0001121978. Our client had an incredibly high number of users in their environment, and that analysis was bringing the system to a screeching halt. The combination of the upgrade, and increase in memory allowed for our initial Full Batch Risk Analysis at the user, role, and profile level to complete successfully without any errors.

After all three initial background jobs were completed successfully (Full Sync, Batch Risk Analysis, and Management Report), ERM was able to successfully utilize RAR's ruleset to perform the analysis prior to generating the role in the backend.

Hope this helps someone in the future.

Thanks,

Phil

[kurtthomas_hollis]

Hi Phillip:

Make sure no RAR jobs are running and all the Batch loads are completed for the system you are using for RAR analysis.

Kurt Hollis.

[Former Member]

Hi Philip

Try following steps:

1. In ERM go to configuration - Miscellaneous

2. You will get three boxes for RAR web services with user id and password.

3. Change all of these three user id/password to some other user id and save.

4. After that change it back to the correct /original user id and password and save.

Let us know the result.

Best Regards

Asheesh

[Former Member]

Hi Philip,

I agree to the tip you received already.

In addition I will recommend to:

• Verify that the url's towards RAR are set up correctly under config-miscellaneous. (They must refer to the correct host and port numbers).

• Make sure also that all backend connector names are identically set up both in RAR and ERM.

• If you have problems also with risk analysis from CUP and internally in RAR, then the error will be originated from RAR and not related to the communication between ERM and RAR.

Best regards

Kari.

[Former Member]

Thanks for your response Asheesh,

Note: RAR and ERM are deployed on the same server, therefore, web services are not required. However, I did try turning on web service, and changing the user ID and password to an ID that had elevated access, confirmed the password was correct, and still had no luck.

I've also verified that the correct URLs are placed in to the configuration settings, and still no analysis.

Any other suggestions?

[Former Member]

Thanks for your response Kari Anne.

I've verified the URLs in the configurations are correct. I also verified that the web services URL is correct for VirsaCCRiskAnalysisService in the J2EE visual administrator.

Both connectors are named identically in the back end systems. I'm also able to run a user and role level risk analysis in RAR, I just am not able to run it in ERM during the role creation process.

FYI: We also are not implementing CUP.

Any other suggestions?

[Former Member]

Hi,

have you activated the workflow for ERM in CUP. Even if you dont use CUP, wth workflows will need to be activated there. Under configuration -- > Miscellaneous you need to make sure the RE workflow type is there.

Also you need to upload the AE_init_append_data_RE.xml file in CUP. Check the post installation deck if you have them.

Thanks!

Chinmaya

Edited by: chinmaya prakash on Nov 16, 2010 9:51 PM

[Former Member]

Hello Phillip

Can we double check the connector that is being used to communicate between system ?

Kindly check note no : 1136690 - Failed to perform Risk Analysis in ERM.In this note error message is different but still it would good option to double check connector name .

Also I would like to know which version/Service pack of GRC you are using .

I would recommend to Import the latest Initial .XML files into the application.

Importantly, these .XML files have to be in-SYNC with the Support Pack level of the ERM application installed.

Example: You have ERM 5.3 SP10, make sure you download the Initial Data files for the same Support Pack, SP10 from SAP Service Market Place (SMP).

Location on SMP:

Downloads =>SAP Support Packages =>Entry by Application Group =>SAP Solutions for Governance, Risk and Compliance =>SAP GRC Access Control =>SAP GRC ACCESS CONTROL =>SAP GRC ACCESS CONTROL 5.3 =>Entry by Component =>JAVA-Components.

Look for the folder or link "SAP GRC ACCESS CONTROL 5.3 TXT".

This folder contains the Initial Data files for all the Business Objects Access Control applications. Extract the files for ERM (folder name RE) and import into the ERM application as a Post Installation step.

Steps to Import the files:

Go to Configuration =>Initial System Data. Import the files with appropriate option:

1. RE_init_clean_and_insert_data.xml - "Clean and Insert" option.

2. RE_init_append_data.xml - "Append" option.

Do let us update about the status of this issue ?

Thanks & Regards

Asheesh