home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!cherokee!rivera!yslas
- From: yslas@riverauswest.com ( Rob Yslas)
- Newsgroups: comp.databases.sybase
- Subject: Re: Question: Transaction log
- Message-ID: <1992Sep15.181757.25100@advtech.uswest.com>
- Date: 15 Sep 92 18:17:57 GMT
- References: <1992Sep15.124446.21526@uni-paderborn.de>
- Sender: yslas@rivera ( Rob Yslas)
- Organization: U S WEST Advanced Technologies
- Lines: 26
- Nntp-Posting-Host: rivera.advtech.uswest.com
-
- In article <1992Sep15.124446.21526@uni-paderborn.de>, hackes@uni-paderborn.de (Markus Brakweh) writes:
- > Hi folks.
- >
- > I'm working with Accell/Sybase and got an astonishing effect.
- >
- > When I gave the 4GL command 'update current record'
- > I got the error message 'Transaction full.....' although I dumped the tran some seconds before.
- >
- > Then I wrote 'insert into .....' instead of 'update current record' everything
- ^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
- Seems to me that Sybase handles these two situations differently. If you are
- updating the transaction log will keep two copies of the row(s), before and after
- the transaction is completed. When a dump transaction command is issued the
- log is up to the most recent checkpoint. This may be related to how much space
- the dump actually returned for logging purposes. You may want to try running the
- checkpoint command prior to the dump transaction or if you don`t care about the
- transaction log you may want to dump transaction with nolog or dump transaction
- to the null dump device.
-
- Good luck,
- Rob
-
-
- --
- yslas@uswat.uswest.com
- Thanks
-