topic Re: Workload Statistics collector issue in Application Development and Automation Discussions

Workload Statistics collector issue

vijay_kumar134 — Mon, 15 Apr 2013 12:53:37 GMT

Hi,

We have created the custom program for Workload Anaysis, here the usage analysis program (scheduled in Background) reads the information from local system statistics data (STAT.DAT) and appends the same in the flat file at OS level.

STAT.DAT is a local application server specific temporary storage that is used by SAP for transferring the contents from SAP Buffer and the contents of the file are DYNAMICALLY updated/refreshed by SAP.

a. Current size of STAT.DAT file - 100MB

b. Frequency & situation of update/refresh to STAT.DAT - Controlled by SAP

As per the our current logic, our current custom program fails to capture all the tcode usage details.

Our Justification Below:

1. Usage Analysis program reads the static information available in the STAT.DAT file at fixed intervals.

2. STAT.DAT file is DYNAMICALLY updated/refreshed by SAP.

3. Whenever the STAT.DAT file refreshed , Unprocessed / Unread data in the STAT.DAT will be lost (not captured by Usage Analysis program)

Please anyone guide me to solve the data loss issue.

Thanks.

Viji.

Re: Workload Statistics collector issue

RaymondGiuseppi — Tue, 16 Apr 2013 07:16:02 GMT

I suppose you call SAPWL_STATREC_READ_FILE / SAPWL_STATREC_DIRECT_READ or similar tool to read the data, else can you elaborate ;

Are you sure that you get the data from each and every server available (use of TH_SERVER_LIST advised) Else try to reduce interval of execution or ask basis to increase allocated space for storage

Regards;

Raymond

Re: Workload Statistics collector issue

vijay_kumar134 — Tue, 16 Apr 2013 07:49:34 GMT

Thanks for your respose Raymond.

We are using FM : SAPWL_STATREC_READ_FILE

Might be the interval period data has been lost.

Re: Workload Statistics collector issue

RaymondGiuseppi — Tue, 16 Apr 2013 08:34:21 GMT

Also check for OSS notes on this now obsolete FM that SAP maintains until every standard report has been upgraded, there were some problems and corrections.

Look also in your system to jobs like SAP_COLLECTOR_FOR_PERFMONITOR, should be executed every hour, so should your job.

Also in you report, you could read table TBTCO with information from GET_JOB_RUNTIME_INFO to compare scheduled date/time of execution and actual start, so raising a message when job was delayed.

Regards,

Raymond