Re: Infinite Recovery Help Needed (Online 5.0)

From article <1993Jul23.154202.17436@informix.com>, by davek@newjersey.informix.com (Dave Kosenko): > > andrew.shaw writes: > |> Another suggestion was to lower the high-water parameters by 10 from > |> the current default values. However, it appears that this also does not > |> solve the general case; if the offending transaction spans too long a > |> period, the logs can fill with other traffic, which if they are also > |> committing or rolling back when the high-water mark is reached, might > |> occupy the space needed to rollback the offending transaction. > > You can always set the LTXHWM and LTXEHWM to 50, which guarantees that you > will always be able to rollback any LTX situation (actually, the "true" > threshold is probably higher since rollback records, CLRs, are only 24 bytes > in length, which is smaller than any possible other log record for > transaction processing, but 50 eliminates having to think about it). The > LTXEHWM will block any other transactions until the LTX is done rolling > back. Thus the general case is solved. > Thanks Dave, and everyone else who weighed in on this knotty problem. Andrew Shaw AT&T Bell Labs andrew.shaw@att.com apache!shaw@att.com