Scribd
Upload
156 views4 pages

File Names For Developer Traces

The document discusses file names used for developer traces in SAP systems and parameters for configuring system traces. It also provides steps for configuring STMS and transport routes between different systems like development, test, and production.

Uploaded by

Anant Singh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
156 views4 pages

File Names For Developer Traces

The document discusses file names used for developer traces in SAP systems and parameters for configuring system traces. It also provides steps for configuring STMS and transport routes between different systems like development, test, and production.

Uploaded by

Anant Singh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

File Names for Developer Traces

Component Dispatcher Work process /task handler Gateway Message server Internet Communication Manager (ICM) SAP Web Dispatcher RFC (Remote Function Call) facility

File Name dev_disp dev_w<n>, whereby n is the number of the work process dev_rd dev_ms dev_icm dev_wdisp dev_rfc, dev_rfc<n> dev_rfc traces RFC calls to external functions (written in C or Visual Basic). dev_rfc<n> traces RFC calls that are executed in SAP work processes. <n> is the number of the work process in the server (as shown above). A work process uses the same log file across RFC calls. dev_lcom dev_eq<n> Standalone enqueue server: dev_enqrepl, dev_enqsig, dev_enqsrv, dev_enqwork, dev_enqio_<n>

FastRFC Enqueue (lock)

Startup (sapstart) R3trans and tp transport programs Monitoring infrastructure (test mode only)

dev_sapstart dev_tp dev_moni In normal operation, you will not see this file. It is used only by test tools of the monitoring infrastructure. It therefore appears only if the test tools must be activated during a support session.

System Trace: Relevant Profile Parameters


With system profile parameters, you can set the maximum size of the SQL and system trace files and specify 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 rstr/buffer_size_kB Meaning The SAP trace (for example, SQL trace) saves the trace data in trace files. To minimize the effect on system performance the data is saved in an internal buffer, and not saved directly. Profile parameterrstr/buffer_size_kB determines the size of the buffer in kilobytes.

rstr/filename rstr/max_files rstr/max_filesize_MB

The SAP trace (for example, SQL trace) stores the data in several files that are written sequentially. Parameter rstr/filename defines the base name of these files. There is always one file with this exact name. Wenn die Datei voll ist (Parameter rstr/max_filesize_MB), wird die Datei umbenannt und eine neue Datei mit dem Basisnamen erzeugt. When the file is renamed, a number between 00 and 99 is assigned to the file name. Parameter rstr/max_files determines the maximum number of files. If this number is exceeded, the files are overwritten.

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=<n> option set to the instance. We can even use the SM50 and choose the WP and activate the trace or increase/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 file location. Usually it is /usr/sap/SID/D*/log/TRACE To view ST01-->Analysis (once trace is on and activity is completed Trace off then we can view this ) These are used to record the SAP internal activities.

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

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. 2. After SAP Gui installed. (Development system is always domain controller.) 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.

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.

You might also like