ST05 SQL Trace and DBACOCKPIT SQL Command Window issues

[] [] [] []

Symptom

This note describes problems with the ST05 SQL Trace and SELECT statements in the DBACOCKPIT SQL Command Window.
When viewing the ST05 SQL Trace, entries classified as EXECIMM or EXECSTA either show table name “Tunknown” or the table name from the previous SQL statement.When executing SELECT statements using the SQL Command Window in transaction ST04 or DBACOCKPIT, integer values larger than 8 digits are cut off.

Solution

Apply the latest lib_dbsl patch from SAP Service Marketplace.
This DBSL patch adds two additional lines in each developer trace file at startup. These lines appear as follows:
C SAP patchlevel
C SAP patchno
C Last MSSQL DBSL patchlevel
C Last MSSQL DBSL patchno
C Last MSSQL DBSL patchcomment ()
The lines labelled “Last MSSQL DBSL” are the same as before. The two lines starting with “SAP” are new. The SAP patch number is the same as you will see when you examine the file properties using the Windows Explorer. Usually, the “Last MSSQL DBSL patchno” is the same as SAP patch number, but not always. If the SAP patch number is higher, this means that other components were patched along with the MSSQL DBSL component in the same patch delivery.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment