home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!kddlab!jcpltyo!ohayon
- From: ohayon@jcpltyo.JCPL.CO.JP (Tsiel Ohayon)
- Newsgroups: comp.databases.sybase
- Subject: Re: Recovering from a log segment full condition
- Message-ID: <145@jcpltyo.JCPL.CO.JP>
- Date: 17 Dec 92 23:57:22 GMT
- References: <1992Dec16.205611.19776@spectrum.xerox.com>
- Organization: James Capel Pacific Limited, Tokyo Japan
- Lines: 23
-
- In article <1992Dec16.205611.19776@spectrum.xerox.com> sauvain@wrc.xerox.com 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.
-
- Try the following sql statement:
-
- 1> dump transaction ticdsf with no_log
- 2> go
-
- It should solve your problem
-
- Tsiel
- --
- ----8<--------------------------------------------------------------->8------
- Tsiel:ohayon@jcpl.co.jp | If you do not receive this E-mail, please let me
- Employer may not have same | know as soon as possible, if possible.
- opinions, if any ! | Two percent of zero is almost nothing.
-