NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/database/sybase/521

Text File | 1992-12-21 | 1.5 KB | 46 lines

Newsgroups: comp.databases.sybase
Path: sparky!uunet!psinntp!kripalu!harit
From: [e-mail]
Subject: Re: Recovering from a log segment full condition
Message-ID: <1992Dec18.170126.269@uunet!cbmvax!xmws!kripalu>
Sender: harit@uunet!cbmvax!xmws!kripalu
Reply-To: [e-mail]
Organization: Kripalu Center
References: <[e-mail]>
Date: Fri, 18 Dec 92 17:01:26 GMT
Lines: 33

In article <[e-mail]>
[e-mail] (Richard Sauvain) writes:
> I have run into the following catch-22:
>
> My transaction log fills up (even though I allowed more than 2X data size for
> the transaction log), and when I try to dump the transaction log, I get an
> error message saying that the log segment is full and I should dump the
> transaction log.  Using ALTER DATABASE to increase the size of the segment
> allows the dump to proceed for a while, but we eventually get to the same
> state.
>
> Does anyone understand what is going on here?  Could it be that deleting the
> transaction log is itself a logged operation?
>
> ---
> Name:  Richard Sauvain               | Xerox Webster Research Center
> Email: [e-mail]         | Mail Stop 128-27E
> Phone: [phone]                | 800 Phillips Road
> Fax:   [phone]                | Webster, NY 14580  USA
>
> --------
> The gory details:
[Deleted]

Unless you use the "with no_log" option on the dump tran command it is in fact
logged.


--
Michael Allen Latta
Kripalu Center
[e-mail]
[phone]