Generation of numerous archivelogs when running a batch risk analysis

Question

Is it a normal process to generate so many ARCHIVELOGS when running a batch risk analysis?  If the jobs are broken up into three seperate processes, we use approximately 7GB.  If we run all the processes into one, we use 100+GB. What storage requirements should we anticipate is needed in DEV and PRD for the generation of ARCHIVELOGS ?

Answer 1

I found a forum question that has information that resolved our issue.  The following is the link:  https://forums.sdn.sap.com/click.jspa?searchID=14313475&messageID=5373262
Q: Background jobs to analyze users against our rules are taking forever. Our feeling is that the problem lies in the R/3 backend, however we need to know how to improve performance.
A: Step 1
Please ask your SAP BASIS to apply the following notes:
Note: 1044174 - Recommendation for CC 5.x running on Oracle 10G Database
Note: 1121978 - Recommended settings to improve performance risk analysis
Note: 1044173 - Recommended NetWeaver Setting for Access Control 5.x
Note: 723909 - Java VM settings for J2EE 6.40/7.0
Step 2
Once you applied all of the above SAP notes. Please ask your SAP DBA/BASIS to do the following actions:
Truncate table virsa_cc_prmvl; this is the table which stores all the analysis results.
Execute stats on all virsa_cc* tables. Example: exec dbms_stats.gather_table_stats ('SAPSR3DB',VIRSA_CC_PRMVL)