FreeTDS Development Group

[Michael Peppler <mpeppler AT peppler.org>]

On Thu, 2002-10-24 at 12:40, Frediano Ziglio wrote:
> What does it mean this error ?
> 
> Space available in the log segment has fallen critically low in database
> 'tempdb'.  All future modifications to this database will be suspended
> until the log is successfully dumped and space becomes available.

You (or someone else) have/has run a query/procedure that has filled up
the log in tempdb. This usually means that tempdb is too small for the
type of query that you're running.

To get out of this you can do a couple of things.

1. You can increase the size of tempdb.
2. Kill the process that is holding all of the log space. You can
usually find this info by querying master..syslogshold.
3. To stop it from happening again you can set the "abort on log full"
option for tempdb. This will cause any query that fills the log to get
aborted rather than ending up in "log suspend" mode.

Dumping the log in tempdb normally won't help as "trunc. log on
checkpoint" is on by default in that database. If the log fills up it
means that there is a process that has an open transaction that is
filling up the log (the log can never be truncated past the most recent
open transaction).

Hope this helps.

Michael
-- 
Michael Peppler / mpeppler AT peppler.org / http://www.mbay.net/~mpeppler
mpeppler AT zetatools.com / ZetaTools, Inc / http://www.zetatools.com
ZetaTools: Call perl functions as Sybase stored procedures!

Attachment: signature.asc
Description: This is a digitally signed message part