cancel
Showing results for 
Search instead for 
Did you mean: 

Generation of numerous archivelogs when running a batch risk analysis

Former Member
0 Kudos

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 ?

Accepted Solutions (1)

Accepted Solutions (1)

former_member366047
Contributor
0 Kudos

Gregory-

Archive Logging can be turned off to conserve space. I believe it is done in the database level...

Ankur

Former Member
0 Kudos

Our DBA doesn't feel comfortable turning it off. Is it standard practice to turn this off and does everyone turn theirs off?

former_member366047
Contributor
0 Kudos

CC 5.x generates large-sized logs. It is common practice to turn it off to conserve space...

Ankur

Former Member
0 Kudos

So, if the system crashes and archivelog creation is turned off, how do you rebuild?

former_member366047
Contributor
0 Kudos

Archive logging is a separate function from DB Archiving...

Ankur

Former Member
0 Kudos

DB archivelogs are what is being generated and in large amounts. The file sizes vary from 45Mb and 52Mb each and are built at a rate of about 5Mb a second. We can generate many, many of these files when running an incremental batch risk analysis. Has anyone else seen this issue? Is this normal?

Answers (1)

Answers (1)

Former Member
0 Kudos

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)