cancel
Showing results for 
Search instead for 
Did you mean: 

GRC 10 - AC - Table GRACUSERPRMVLEXT and Disk Space

Former Member
0 Kudos

Hi All,

Scenario:

We have implemented AC 10 (service pack 9).
Due to our disk space being limited, and to facilitate testing, we have run the background risk analysis job and deleted the output on a number of occasions.

Following each deletion and re-run of the batch risk analysis, the number of records being written to the table GRACUSERPRMVLEXT (User Permission Violations for Extended Objects) has increased significantly.

The initial run generated 90 million records; the second run generated 130 million records; and the third run generated 160 million records.

The ruleset and user data has not changed significantly since the initial run. We have not changed the parameters being used when running a background risk analysis.

Question:

  • What is causing the volume of records to increase on each occasion given that the inputs are remaining constant?
  • Is there any way to limit the number of records generated?

Many thanks in advance.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Maeve ,

Kindly refer below mentioned note for database management for SOD jobs

Note 1580877 - Best practices in storage management for SoD analysis jobs

Kindly refer to section C for recommendation and D for solution .I think you need to run  GRAC_DELETE_ACCESS_RULES  and GRAC_DELETE_ACCESS_RULES_ALL to clean up the table.

We also had same issue and this note fixed the problem

Thanks & Regards

Asheesh