Performance of GRAC_SPM_LOG_SYNC_UPDATE in SPM v10

[Former Member]

Hello guys,

Currently in our platform we have implemented version 5.3 of FireFighter (around 25 systems) and in every system we launch program /VIRSA/ZVFATBAK for updating the log. In the way that is used FireFighter in the company is not strange that we face performace problems with this program (it can take up to several thousands of seconds per day and per system).

Now we are running a pilot to test GRC version 10 and the equivalent program of /VIRSA/ZVFATBAK is called GRAC_SPM_LOG_SYNC_UPDATE. This program is launched just in the central SPM system and the first question that arose was to know how much will it last. In our first tests looks like it will last a lot.

My question for you is to know if someone has real experience with version 10 (and also had in 5.3) and in that case how much last program GRAC_SPM_LOG_SYNC_UPDATE compared with /VIRSA/ZVFATBAK.

Thanks,

Félix

[Former Member]

By the way, There are a couple of notes (1618040 y 1617483) that are related with GRAC_SPM_LOG_SYNC_UPDATE and performance. We will install them in 2 or 3 days and we will try to see if we can see any difference.

[Former Member]

After installing those notes in a lab system, we didn´t find any relevant difference.

[Former Member]

Unfortunatle this log sync call for Action usage sync again ,if im not wrong.

and it checks for stad log of the backend sytem and changelog table and all like older FF user for report.

Regards

Prasant

[Former Member]

Hi there,

We have just upgraded to SP08 on GRC and the R/3 target systems but still have incredibly slow performance:

GRCPINW       V1000_700 0008      SAPK-10308INGRCPINW      SAP GRC NW Plug-in

GRCFND_A     V1000 0008             SAPK-V1008INGRCFNDA     GRC Foundation ABAP

This is even if I run the job for a specific connector, 1 FFID, 1 Firefighter and 1 day only (as recommended in not:  Note 1617529 - Best Practices For Improving Performance of EAM Log Sync job.

I was just wondering if anyone else out there had found a solution to this?

Regards,

Lisa

[simon_persin4]

Hi Lisa,

Have you got an index on the CDHDR table in the target systems?

If not, put one in for fields:

MANDANT,

USERNAME,

UDATE,

UTIME.

That normally improves performance by about 80%.

Simon

[Former Member]

Hi Simon,

Thank you for this good advice - we've added the indices and it resulted in greatly improved performance!

Much appreciated :-),

Lisa

[sebastian_konrad]

Dear Simon,

the Option with the Index is nice.

But we are useing the Firefighter with 40 productive systems and 40 Testsystems.

So nobody wants to add the index manually.

Do you still have another option which we can use?

Thanks & Regards,

Sebastian Konrad

[simon_persin4]

Hi Sebastian,

The index can either be transported or applied manually depending on your client settings and policies?

That really is the option for improving the performance of this report.

Simon