Traces 
You can use various traces to obtain detailed information on the actions of the database system.
Note
Performance may get worse while a trace is being written. Therefore switch off the trace as soon as the actions necessary for the analysis have been logged.
As long as a trace is being written, operate the database with the lowest possible load and execute only those actions that are necessary to reproduce the error.
Procedure
Default File Name |
Default Directory |
Description |
How to Use the Trace |
|---|---|---|---|
knltrace |
Run directory of the database (see Run Directory). To change the location of this file, use the database parameter KernelTraceFile, see Support Database Parameters. Note that the trace messages are first written to the main memory. To generate the trace file, you need to flush the database trace. |
Contains the messages of the database trace You can use the trace file to identify errors, such as those that occur while processing SQL statements. Note that activating the database trace has a negative effect on performance only with SAP liveCache databases. This is not the case with SAP MaxDB databases. The trace file is written in binary format. To display the trace file, use Database Studio, Database Manager CLI or CCMS. |
|
odbctrace-<pid>.prt |
Microsoft Windows:<data_path>\wrk Unix/Linux:<user_home>/.sdb/<computer_name> |
ODBC trace The system can log SQL statements, communication packages, method calls, and call parameters. <pid> = Process ID |
Use the odbc_cons database tool. More information: ODBC Manual, Troubleshooting Using the SAP MaxDB ODBC Trace |
User-defined |
User-defined |
JDBC trace The SAP MaxDB JDBC driver logs all JDBC API calls and their input parameters, return values, and the corresponding thread. |
Specify the corresponding option for establishing the connection. More information: Java Manual, JDBC Trace |
sqldbctrace-<pid>.prt |
Microsoft Windows: <data_path>\wrk Unix/Linux: <user_home>/.sdb/<computer_name> |
SQLDBC Trace The system can log SQL statements, communication packages, method calls, and call parameters. <pid> = Process ID |
Use the sqldbc_cons database tool, or the CCMS in SAP systems. More information:
|