Traces 
You can use various traces to obtain detailed information on the actions of the database system.
Note
Performance can decline while a trace is being written. You should 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 Activate the Trace |
|---|---|---|---|
knltrace |
Run directory of the database: <independent_data_path>\wrk\<database_name> |
Database trace The system logs all messages from the kernel. You can use the log 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. |
|
odbctrace-<pid>.prt |
<user_home>\Application Data\sdb (Microsoft Windows) <user_home>/.sdb (Unix/Linux) |
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 |
Your choice |
Your choice |
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 |
<user_home>\Application Data\sdb (Microsoft Windows) <user_home>/.sdb (Unix/Linux) |
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:
|