8/2/2019 File Names for Developer Traces

1/4

File Names for Developer Traces

Component File Name

Dispatcher dev_disp

Work process /task handler dev_w, whereby n is the number of the work process

Gateway dev_rd

Message server dev_ms

Internet Communication Manager(ICM)

dev_icm

SAP Web Dispatcher dev_wdisp

RFC (Remote Function Call)facility

dev_rfc, dev_rfc

dev_rfc traces RFC calls to external functions (written in C

or Visual Basic).

dev_rfc traces RFC calls that are executed in SAPwork processes. is the number of the work process inthe server (as shown above). A work process uses the samelog file across RFC calls.

FastRFC dev_lcom

Enqueue (lock) dev_eq

Standalone enqueue server: dev_enqrepl, dev_enqsig,dev_enqsrv, dev_enqwork, dev_enqio_

Startup (sapstart) dev_sapstart

R3trans and tp transport

programs

dev_tp

Monitoring infrastructure (testmode only)

dev_moni

In normal operation, you will not see this file. It is used onlyby test tools of the monitoring infrastructure. It thereforeappears only if the test tools must be activated during asupport session.

System Trace: Relevant Profile ParametersWith system profile parameters, you can set the maximum size of the SQL and system trace files andspecify its path name. All trace parameter names begin with the string rstr/. You can display the

standard values and the parameter documentation in transaction RZ11.The trace parameters that you can set are as follows:

Profile Parameter Meaning

rstr/buffer_size_kB The SAP trace (for example, SQL trace) saves the trace data in tracefiles. To minimize the effect on system performance the data is savedin an internal buffer, and not saved directly. Profileparameterrstr/buffer_size_kB determines the size of the bufferin kilobytes.

http://help.sap.com/saphelp_nw2004s/helpdata/en/1f/8311594bc511d189750000e8322d00/frameset.htm

8/2/2019 File Names for Developer Traces

2/4

rstr/filename The SAP trace (for example, SQL trace) stores the data in several filesthat are written sequentially. Parameter rstr/filename defines thebase name of these files. There is always one file with this exactname. Wenn die Datei voll ist (Parameter rstr/max_filesize_MB),wird die Datei umbenannt und eine neue Datei mit dem Basisnamenerzeugt. When the file is renamed, a number between 00 and 99 is

assigned to the file name. Parameter rstr/max_files determinesthe maximum number of files. If this number is exceeded, the files areoverwritten.

rstr/max_files

rstr/max_filesize_MB

The System maintains additional trace parameters which you should not change.

You can obtain further information on the parameters using transaction RZ11.

There are two types of traces:

One is Developer trace other one is system trace.

Developer Trace:

rdisp/TRACE= option set to the instance.

We can even use the SM50 and choose the WP and activate the trace orincrease/decrease the trace.

Default location in OS level is /usr/sap/SID/D*/Work

Can be see from St11 or at OS level.

These are recommended for system monitoring and problem analysis.System Trace:

ST01/ST05 We can on/off the trace for particular activity .

rstr/filename this profile parameter is used to set the location of the System trace filelocation.Usually it is /usr/sap/SID/D*/log/TRACE

To view ST01-->Analysis (once trace is on and activity is completed Trace off then wecan view this )

These are used to record the SAP internal activities.

du -h oraarch ( Directory name ) : TO check directory space.

8/2/2019 File Names for Developer Traces

3/4

df -h | grep /dev/cciss/c0d0p3 | cut -c 41-43

This command displays the following on my machine

85%

Basically this command makes 'df' display the disk usages of all the partitions and

then extracts the lines with /dev/hda1 since I am only interested in that. Then it

cuts the characters from the 41st to the 43rd column since they are the columns

that display the usage in % , which is what I want.

D

u -hs /home/*" as root will give you the size of each directory in /home.

"du -hs /home/* | sort -r" will sort them from largest to smallest.

STMS Configuration and Transport Route Configuration

1. After SAP Gui installed. (Development system is always domain controller.)

2. Logon to Client :000

User: DDIC.

Pwd: ******

3. Put a T-code (se06) in the command field.

4. Click standard installation and click post installation (yes)

5. Put a T-code (STMS) in the command field and give a description then save it.

6. Click System overview push botten, click extras option from the menu and click

Distribute and activate configuration. (Yes)

7. Back to the stms main screen and click Transport routes from the push botten.8. Click Configuration button from the Menu.

9. Click Distribute and activate from the configuration menu.

10. Now your sap system is activate in domain controller.

11. Now logon to QAS system.

8/2/2019 File Names for Developer Traces

4/4

12. Client: 000

User: DDIC

Pwd: ****

13. Put a T-code (se06). In the command field.

14. Click standard installation and click post installation (yes)

15. Put a T-code (STMS) in the command field.16. Click other Configuration push butten in the bottom of appear screen.

17. Give information about development system. Example: tisdev, 00

18. Then save it. Ok

19. Now QAS is waiting for include domain controller.

20. Logon to Development system.

21. Click system overview push butten.

22. Click sap system from the menu.

23. Select the QAS systems.

24. Click Approve butten from the sap system menu.

25. Now QAS is member system of domain Controller. (Development system).

26. Suppose if you want configuring Production also, following the same step in the

QAS.