FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: October 25, 2002 4:49 PM
>
> 1> select * from master..syslogshold
> 2> go
> Msg 1703, Level 10, State 2, Server , Line 1
> Failed to allocate disk space for a work table in database 'tempdb'. 
> You may be able to free up space by using the DUMP 
> TRANsaction command,
> or you may want to extend the size of the database by using the ALTER
> DATABASE command.
> 
> 1> 
> 
> After some time disappear... I have this error mainly with test 0014
> (dblib) but I don't know why... This problem never raise before...

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?  

>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" ?  

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.  

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?  

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.