What happens when you truncate table virsa_cc_prmvl in GRC RAR 5.2

[Former Member]

Hi All.

We would like a bit of advice if possible.

We have just done a successful upgrade of RAR 5.1 to 5.2.

There are several threads on the forum about speeding up RAR response, and some mention

u201Ctruncate table virsa_cc_prmvlu201D

Our production system lists this table as being 12GB and having 60 million rows and data going back until the initial loads done in 2007.

When you look at the first 1000 rows in debug, it appears to be the detailed report.

Just for info our Development system list the table as being 11Gb

So the question is straight forward, will there be any data loss or will it affect any reports if we run u201Ctruncate table virsa_cc_prmvlu201D

As the u201Ctruncate table virsa_cc_prmvlu201D process will delete all the rows from within the table.

Kind Regards,

Terry Carter

SAP Security Consultant

su53solutions

SPECIALISTS IN SAP® SECURITY & GRC

[koehntopp · Accepted solution]

Terry,

virsa_cc_prmvl hold the data from background risk analysis. If this table is big, this is a sign that youranalysed systems have many violations. It also holds the results from offline analysis and management reports.

Truncating this table will rid you of that information. I would not recommend doing that.

You could try to do a full risk analysis for all connected systems, with update to management reports and offline analysis, to find out if the cleanup activities you have done so far will bring down table size.

Kind regards,

Frank.

[Former Member · Accepted solution]

Hi Frank.

Thank you for quick response, and the great advice

We need to keep the Management report data and the offline analysis

So we wonu2019t be truncating the table.

Kind Regards,

Terry Carter

SAP Security Consultant

su53solutions