Re: what is holding the log in this session

I understand that DDL has to be logged, but once it's logged, why would it hold onto the log as an uncommitted transaction ? ----- Original Message ----- Subject: Re: what is holding the log in this session Date: Mon, March 3, 2008 8:32 From: "TBP (The Big Potato)" <TBP@NotHere.Co.Uk> Floyd Wellershaus wrote: > > I have a session that is running stuff from ec code in an ids10 non > > logged database. I know that at the beginning of the program, some > > indexes are created, and lots of inserts happen to a table. > > This is a batch process that takes over 24 hours to run. It has > > continued to abort with long transaction. > > > > So I have added more logs and am watching it. It is not actually filling > > the logs, other processes are, but what I want to know is, what thing is > > causing a log to act like this transaction is going on, that keeps this > > whole process tied to that log ? > > > > Are there any onstats I can do to look in the logs or anyway find out > > what is happening here ? > > I really can't make heads or tails out of onlog to be able to tie it to > > a sid or see if it's an open transaction etc.. > > > > Thanks for your advice. > > > > Floyd > > > DDL? > > For example extent additions have to be logged. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > >