on 08-07-2012 4:11 PM
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:
Many thanks in advance.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.