Firefighter logs coming up incomplete

[Former Member]

When running the log report I am getting inconsistent results, sometimes there is no file or some of the transactions used are not listed or I get accurate results.

I have looked through the SAP notes listed in previous posts but nothing appears to be relevant. The data is appearing in STAD but it does not look like it is being collected by the batch job.

All the config settings in FF are correct, I have created two jobs to make sure nothing is missed and the jobs are running.

Any help or new ideas would be appreciated.

Thanks,

Roger

[Former Member]

Hello Roger,

Here are the things you can look at:

1. First check and make sure that you have followed the SAP Note 1039144. Please refer to the second section of this Note (excluding the section for index creation). Make sure that you have scheduled the job on hourly basis with default variant. Please do not run multiple jobs. If you have multiple jobs running, please cancel alll and schedule a fresh job which is running on hourly basis with default variant. Make sure that the job class in SM36 is A.

2. Please run transaction SE37 and give the name of function module as TH_SERVER_LIST. Click on Execute button and hit execute again on the subsequent screen. At the output screen of the function module, click the icon with a number (at the bottom of the screen) to see the output of this function module. Here you should see the list of application servers that you have in your system and entry for each one of them. Please check the entries in the SERV column. The entries in this column should begin with sapdp.. for eg. sapdp00, sapdp01 etc... if there is anything else for any of the app. server then you need to make an entry in the service file of your system to correct the same. The working of FireFighter background job in highly dependent on these correct entries. If you will search the OSS for any SAP Notes, you can find SAP Notes related to it if you search based on criteria TH_SERVER_LIST. Check the ones in the GRC component.

3. Check in SM37 if any of the FireFighter jobs are getting delayed or getting cancelled. Check SM37 for STATcollector job as well to see if that is getting delayed or cancelled. If this is the case with any of the jobs, then correct the same.

4. Make sure that there is no timezone difference in your system where the time zone of the batch user with which you have scheduled the FireFighter background job is different from the system time zone. To check if you have any time delay problem please do the following:

-> Check the system time from Menu -> Status.

-> Log in via a FFid and do any transaction and immediately log off. Note the system time on which you did this.

-> execute transaction STAD and look for the time shown of the activities that you performed above in step 2.

-> In a correct system, the time should match, however, if in your case it does not then as your BASIS team to correct the same.

5. Make sure that you are on latest support pacakge.

6. Make sure that you have the configuration to log change data set to yes.

6. If none of the above help you, then log a message with GRC-SAC-SFF support and they would be able to help you.

Regards, Varun

[Former Member]

After a lot of trial and error this was a timing issue with the system. We worked out that when daylight saving hours came into place this is when we started losing data, the system time did not match the batch user, changes the batch user to match and everything is working ok now.

Thanks,

Roger