RE: ontape -c
The only way I can think of is
--------------------------
select longtxs, logspused, maxlogsp fromsysmaster:syssesprof where sid = <session id>
maxlog is the number of logical log in bytes
You can try to delete one row and then calculate the
total logical log required for bulk delete.
or else you can turn off the logging
regards
--- Alanoly Andrews <AlanolyA@planmatics.com> wrote:
>
> On the subject of "long transactions":
>
> Has anyone got some numbers and figures on the
> actual size of a logical
> log entry when deleting a row from a table? I
> suppose it is a function of
> the
> row size. I want to be able to calculate in advance
> how many rows can be
> deleted from a table (without a commit) before
> running into the LTHWM
> (whatever that is set for). Assume that no other
> transactions are done on
> the Server during the mass delete from the table.
>
> Thanks.
>
> Alanoly J. Andrews
>
> > -----Original Message-----
> > From: Art S. Kagel [SMTP:kagel@bloomberg.net]
> > Sent: Tuesday, October 12, 1999 3:41 PM
> > To: informix-list@iiug.org
> > Subject: Re: ontape -c
> >
> >
> > No. It is the log size times the number of
> logical logs that determines
> > how large of a transaction can be handled without
> a Long Transaction
> > rollback being triggered (along with the volume of
> other transactions of
> > course) not the size of each log. So if you have
> 5 500MB log files you
> > can safely replace them with 25 100MB log files.
> Just note that with
> > smaller log file sizes it is VERY important to set
> LBU_PRESERVE which can
> > be ignored if you have huge log size.
> >
> > Art S. Kagel
>
=====
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com