GRC 5.3 backround jobs

[Former Member]

our system has 130 GB total include abap, java and GRC.

we have 3710 users, 3304 role, 1211 profiles in the backend system

the 3 full jobs tooks 80gb of the free space.

now i need to run the full jobs again and i have only 5 gb left.

1. is there a job that clean the records in the database.

2. is that normal that it takes so much space?

thanks

Sigal

[Former Member]

thanks I will use Create Exclusion Object, but my problem now is that my database is too big and I don't have space left.

is there a away to clean the older data from previous background jobs?

Sigal

[Former Member]

Read my first post how to delete the spool files.

BTW If you have enabled the system for offline risk analysis the analysis is also saved in table PRMVL. This table can grow really big.

You find the setting in RAR>>Configuration>>Risk Analysis>>Additional Options.

[Former Member]

If you only use role based autorizations then you can omit analyzing the profiles. You can also exclude analyzing sap standard roles. You have an option to exclude objects when defining a background job. If you exclude the value SAP_* you should be ok.

You might also have some powerful roles that is something similar to SAP_ALL which you might consider to exclude from the analysis.

This will reduce false positives, spool file sizes and analyze time.

[Former Member]

Background jobs perform SOD analysis and stores data for Off line risk analysis. I would say use "Object exclusion functionality" that will help you to reduce the size of the data generated by batch risk analysis.

Parveen

[Former Member]

Hi Sigal,

The spool files can be enormous. it is normal.

You can delete the spool files in RAR>>Configuration>>Background Job>Search. Mark the jobs and delete them.

Vit

Edited by: Sorry. I don't think it will delete the content in table prmvl.

Edited by: Vit Vesely on Jun 28, 2009 4:40 PM