FreeTDS Development Group

[Frediano Ziglio <freddyz77 AT tin.it>]

> 
> Frediano, 
> 
> Earlier you wrote: 
> 
> "After a bit of time I think Sybase extend log and continue... program
> finish with success... and subsys file under /opt/sybase-11.9.2 became
> bigger and bigger (yesterday was 61MB, now 62)."
> 
> Does that mean that your transaction log is 61 MB?  
> 

I don't know... I think my db is in two file: device and subsys under
/opt/sybase-11.9.2. I installed this server only to do some test...

Also I noted that my partition was quite full... perhaps this was the
real problem...

> >From what you're saying, it sounds like there's an open transaction.  The
> log cannot be truncated until the transaction is committed.  What says "DBCC
> OPENTRAN tempdb" ?  
> 

1> dbcc opentran tempdb
2> go
Msg 102, Level 15, State 1, Server , Line 1
Incorrect syntax near 'tempdb'.

1> 

> Two possibilities:
> 
> 1.    a goof on your end, failing to commit a transaction.  
> 2.    a bug in FreeTDS, causing the transaction to be left open when it
> shouldn't be.  
> 
> #2 could be libtdb or in odbc.  
> 

I put a patch in token.c skipping TDS_PARAM_TOKEN token in default
processing. Now the log problem raise every 2/3 time I run t0014, but
after some seconds in continue without errors... I think is the time it
take to truncate the log..

I do some test launching t0014 and waiting some seconds... problem do
not raise in such way...

Even forcing the truncate with "dump tran tempdb with truncate_only"
solve the problem...

> If you can't find the source of the open transaction, you can kill all the
> client connections ("kill <spid>").  That should do it.  Else reboot the
> server.  
> 
> If there is no open transaction before running 0014, and 0014 is exhausting
> your tempdb log, then we have to look for a FreeTDS bug, methinks.  I'll see
> if I can reproduce it.  TDS 7.0 and current CVS?  
> 

No, TDS 5.0 (Sybase do not support 7.0) and CVS 

freddy77