The SAP trace (for instance SQL trace) produces the trace data for the trace files. For performance reasons, this is achieved by having an internal buffer rather than directly. The profile parameter rstr/buffer_size_kB determines how large this buffer in kilobytes.
Since Release 6.10, the SAP trace stores the data in many files. These files are written to sequentially. The parameter rstr/filename sets the essential title of individuals files. Almost always there is one file while using fundamental title. If the file is full (parameter rstr/max_filesize_Mb ), the file is re-named together with a brand new file is created while using fundamental title. When the file is re-named, several from 00 to 99 is defined in to the filename. The parameter rstr/max_files determines the amount of files you’ll find in general. When the number is exceeded. the files are overwritten.
When the RFC/ CPIC time is going beyond threshold value then switch on RFC Trace.
When more buffer swaps occurs in the table buffering ST02. Switch on Buffer Trace.
When the enque or enque wait time is increasing by 5 M.Sec on CI(Central Instance) 100 M.Sec on Dialogue instance (Consider switching enqueue trace)
When there are too many expensive SQL Statements which are increasing the database response time in ST04 then switch on SQL Trace. (Identify those statements in ST04)
Eg. Select * from can be fine tuned by using select single * from with appropriate where conditions.
ST04 > Detailed > Oracle Session > SQL Statements.
Whenever user encounters missing authorizations and could not be traced in SU53 can be traced out by switching the trace on User.
Used to identify the consistency of Kernel. It records all the calls that are made to kernel when the trace is ON.
Note: Do not switch on the traces when they are not required. It will populate enormous log files and occupies the complete disk place and system stands still. As a practice switch on the trace and inform the user to run the transaction. Switch Off the trace.