Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-TWB-TST-P-PA (Application Component) Performance Analysis (Transaction ST05)⤷
SQLT (Package) Trace for SQL, Enqueue, RFC, Memory
Basic Data
| Data Element | SQLTSTAT |
| Short Description | SQL statement (formatted) |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 210 | |
| Decimal Places | 0 | |
| Output Length | 210 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 8 | Statemnt |
| Medium | 13 | Statement |
| Long | 21 | Executed Statement |
| Heading | 55 | Statement |
Documentation
Definition
Depending on the type of trace (SQL Trace, Enqueue Trace, RFC Trace, Table buffer trace), a short form is displayed. If the short form ends with the characters '...', it is incomplete. The short form had to be truncated because of the available output area. You can see detailed information about the logged statement by choosing the "Detail" pushbutton or "Replace Variables".
Double clicking the short form of the statement has the same effect as choosing the "Detail" pushbutton.
SQL Trace
=========
For a logged SQL statement, a shortened SQL statement is displayed, where the variables are replaced as far as this is possible (see below). When replacing the variables in the shortened SQL statement, spaces at the end of variables are suppressed. If the variables contain only spaces, these are reduced to one space.
If the SQL statement contains variables to be replaced, these are listed with "Detail" and replaced in the statement with "Replace Variables" With "Detail", the variables are shown in their full length. With "Replace Variables", space at the end of the variables is truncated.
Note that the current values of the variables are only available for the operations "OPEN", "REOPEN", "EXEC" and "REEXEC", and are therefore only displayed in these cases.
Enqueue Trace
============
For the Enqueue trace, the granules are displayed in this column. If more than one granule exists, they are separated by three spaces. You can see the number of granules in the "Rec" column.
For each granule, the following is displayed, each separated by a space:
- the lock mode
- the table name of the lock object
- the lock argument
The following lock modes are possible:
- Excl(cum) Exclusive lock that can be cumulated
- Excl(non-cum) Exclusive lock that cannot be cumulated
- Shared Shared lock
If there is an exclusive lock, no other user can access the locked object.
A lock in Shared lock mode allows other users to access the locked records in display mode.
You reach the same detailed display by choosing "Var. replace" as by choosing "Detail".
RFC Trace
=========
For an RFC Trace, the following information is displayed:
- The name of the source server on which the function module is (remotely) called.
- The name of the destination server on which the function module is executed
- The characteristic of the server as a client or server
- The name of the executed function module
If one of the specified names cannot be determined from the trace record, "?" is displayed instead.
The system then displays the number of bytes sent and received.
Table Buffer Trace
===============
When accessing buffered tables or structures, the following are displayed - depending on the operation and type of buffering:
- Type of Buffering:
G - Generically buffered
. P - Individual records of the table are buffered
. R - Table completely buffered
. S - Export / import buffering
. C - CUA buffer
. O - OTR Puffer
. E - EMS buffer (export/import to shared memory)
- the length of the key used for access to the buffered table or structure
- the key value with which the buffered table or strucure is accessed
- and sometimes the length of the buffered object
For the 'FETCH' operation, in the case of compressed output, the number of compressed fetches and the average duration of a fetch in milliseconds.microseconds.
For the 'CLOSE' operation, no additional information is displayed.
For the Export/Import buffer trace, characterized by the Load, Retrieve and Invalidate operations, the length of the object is also displayed.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
