AC 5.3 - SPM Log content issue

[Former Member]

Hi,

We are using the SPM (AC 5.3) and are having multiple issues with logs. Following is one issue that I am not able to figure out.

Could you please help me out understanding why this occurs and how to resolve it :

In the logs session/usage data is mixed up. For example ,

          session1 - in July 2012. --- All usage within the session logged properly.

          session2 - in September 2012 --- the transaction used was linked to the previous July session1.

          All sessions after this logged fine.

Thanks !!

[Former Member]

Hello SAMMUKH,

This is a known Firefighter issue. You will need to check if you have any Firefighter ID running

background jobs or mass transactions. The point is that when a Firefighter runs background jobs, it does not start a session. System tries to insert the entries in the most recent session it finds.

You can check this by going to SM37 and search for FF* (if your company has a FF standard), for example. 

You can check SAP note 1586978, which has instructions on how to solve this issue.

Best Regards,

Fernando

[Former Member]

Hi Fernando,

Thanks for your response. I had already gone through the said SAP note. I have checked SM37 for background jobs run by the FF ID. However, there were none. That is where it is getting confusing.

Thanks,

Sammukh

[Former Member]

Hi Sammukh,

Have you checked the timezones?

The user who is scheduling the background jobs must have the timezone in sync with the system timezone.

Also, what is the support pack of your GRC 5.3?

Best regards,

Fernando

[Former Member]

I forgot to mention, you can go to SE38 and use Program TZCUSTHELP to compare Timezones.

Let me know the results,

Fernando

[Former Member]

Hi Fernando,

I am assuming by user you mean the user who runs the background job for /VIRSA/ZVFATBAK.

All timezones are UTC across the system and user.

VIRSANH is at Release 530_700 , SP level 15.

Let me know in case more info is needed.

Thanks,

Sammukh

[Former Member]

Hi Sammukh,

In this case I would recommend to open a message to GRC-SAC-EAM so we can further analyze the issue.

But before opening a message, Could you please show me the complete log report of sessions 1 and 2 described above?

Thanks,

Fernando