## SQLDBC Traces

### Use

There are several SQLDBC traces you can use for troubleshooting and problem analysis.

Traces compromise performance. Use traces only for troubleshooting and problem analysis.

SQLDBC Traces

Trace | Contents
SQL | SQL statements (simplest trace, adequate for most analyses)
PACKET | Communication packages
SHORT | Method calls
LONG | Method calls with call parameters (most comprehensive trace)

To configure, start and stop the SQLDBC traces, use the sqldbc_cons tool.

All SQLDBC traces contain, among other things, profile and time stamp data.

The traces are stored in the directory <user_home>\Application Data\sdb (Microsoft Windows) or <user_home>/.sdb (UNIX/Linux) as the files sqldbctrace-<pid>.prt, where <pid> is the process ID. The trace files are overwritten cyclically.

See also Installation Manual, Directories

### Example

To activate the SQL trace, enter the following command:

sqldbc_cons TRACE SQL ON

Operating system user anna uses the SQLCLI database tool. She uses the SQLCLI database tool to log on to the DEMODB database instance as MONA and queries the data in the CUSTOMER table.

The SQL trace is written in the /home/anna/.sdb/sqldbctrace-19714.prt file:

<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><PRE><PLAINTEXT>SQLDBC 7.6.0 BUILD 004-101-084-288 Nov 15 2004 23:56:34

--- THREAD 4D02 --- 2004-11-19 09:42:27.223840 ---

2004-11-19 09:42:27.224027 [0x8217CC8]

SERVERNODE: ''

SERVERDB : 'DEMODB'

USER : 'MONA'

CONNECT PROPERTIES: (1 entry)

KEY: 'SQLMODE' VALUE: 'INTERNAL'

CONNECT COMMAND: 'CONNECT "MONA" IDENTIFIED BY ? SQLMODE INTERNAL'

SESSION ID: 1

OK

::SET AUTOCOMMIT ON 2004-11-19 09:42:27.279370 [0x8217CC8]

::EXECUTE DBS 'SQLCURS_2' 2004-11-19 09:42:27.279581 [0x8219730]

SQL COMMAND: 'SELECT * FROM CUSTOMER'

RESULT COUNT: -1

CURSOR NAME: 'SQLCURS_2'

::GET RESULT SET [0x8219730]

CURSOR NAME: 'SQLCURS_2' [0x8219E08]

::FETCH NEXT 'SQLCURS_2' 2004-11-19 09:42:27.282629

...