SQL Database Connectivity (SQLDBC) is a runtime environment for the development of database applications and database interfaces for MaxDB. Using SQLDBC, applications can access MaxDB database instances, execute SQL statements and edit data. It consists of the runtime library libSQLDBC, the software development kit SQLDBC SDK, and the tool sqldbc_cons.
SQLDBC offers, among other things, a comprehensive range of trace options which can be called up using the Database or liveCache Assistant. The Tools menu contains the SQLDBC trace tool.
Traces compromise performance. Use traces only for troubleshooting and problem analysis.
Open the Database Assistant (transaction DB50) or the liveCache Assistant (transaction LC10). Choose .
The SQLDBC trace display is part of the DBA Cockpit and can therefore also be called as follows:
Open DBA Cockpit (transaction DBACOCKPIT).
The display options in DBA Cockpit vary depending on which SAP NetWeaver release you are using:
Choose
.SAP NetWeaver 7.1: Choose .
Activating/Deactivating the Trace
To activate the trace, proceed as follows:
Select the required process.
Choose one of the following options:
Trace |
Content |
---|---|
SQL (Switch on SQL trace) |
SQL Statements (simplest trace, adequate for most analyses) |
Short (Switch on short trace) |
Method calls |
Long (Switch on long trace) |
Method calls with call parameters (most comprehensive trace) |
Packet (Switch on packet trace) |
Communication packages |
Enter the size of the trace file.
The trace files contain a file name with convention sqldbctrace-<pid>.prt, where <pid> is the process ID. The trace files are overwritten cyclically.
To deactivate the trace, select the process for writing to the trace and then select Switch Off.
Additional Functions
You can choose the name of the trace file. To do this, choose
.You can choose the size of the trace file. To do this, choose
.Analyzing and Displaying the Trace
Select the required trace file to analyze the trace. Choose Display File.
DBA Cockpit:SAP MaxDB, SQLDBC Trace
SQLDBC Manual, Using SQLDBC Trace