Re: Long Transaction Aborted

From: "Simon Leigh" <simon.leigh@btinternet.com> > >Apparently this is caused by an incorrect setting in the database >can anyone tell me what it is?? Yep, you need to add logs to your database. You don't have enough log space. Check out the onparams command. HTH. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

Obnoxio The Clown wrote: > > From: "Simon Leigh" <simon.leigh@btinternet.com> > > > >Apparently this is caused by an incorrect setting in the database > >can anyone tell me what it is?? > > Yep, you need to add logs to your database. You don't have enough log space. > Check out the onparams command. Either that or break up the transaction into smaller logical transactions if possible. You can do this for an insert cursor by declaring the cursor "WITH HOLD" then you can COMMIT WORK; BEGIN WORK; every N rows inserted, ala dbload and my dbcopy.ec/ul.ec utilities, and avoid the problem. If the load is an unusual event then you may not want to carry the extra logs for the once-a-year load so you can do this instead. It is a good technique anyway so that in the event of a crash the entire job does not roll back. As long as you have a way of picking up where you left off this is great. Art S. Kagel