[egenix-users] unable to trace ODBC usage

[Peter Bengtsson]

M.-A. Lemburg wrote:
> On 2008-01-21 14:37, Peter Bengtsson wrote:
>> I've got a DSN entry that looks like this in /etc/odbc.ini
>>
>> [VAUKLive_Dev]
>> Driver       = FreeTDS
>> Description  = Connecting to VAUKLive_dev
>> Trace        = Yes
>> TraceFile    = /tmp/vauklive_dev-freetds.log
>> Server       = 172.24.66.6
>> Database     = VSODMS1_3
>> Pooling      = No
>>
>>
>> I've tried restarting Apache, restarting Zope and opening, closing,
>> opening and using the connection object in Zope. Nothing starts the
>> trace. The file /tmp/vauklive_dev-freetds.log is never written!
> 
> While ODBC drivers are supposed to use those config settings in
> the odbc.ini file, many of them don't.
> 
> In those cases it is usually better to enable logging at the ODBC
> manager level:
> 
> /etc/odbcinst.ini:
> 
> [ODBC]
> Trace    = On
> TraceFile= /tmp/sql.log

Tried that too. Restarted Zope, restarted Apache and re-opened the 
connection inside Zope but nothing happens.

Could it be that I'm lacking the program that does the actual tracing?
What is it that causes a re-read of the configs in odbc.ini and 
odbcinst.ini?


> 
> You can also enable tracing in FreeTDS:
> 
> /etc/freetds.ini:
> 
> [global]
> ...
> 	# Whether to write a TDSDUMP file for diagnostic purposes
> 	# (setting this to /tmp is insecure on a multi-user system)
> 	dump file = /tmp/freetds.log
> 	debug level = 10

That worked at least but the trace wasn't very helpful. The file managed 
to grow to 2.5M on one test!

-- 
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com