Re: Summary: Online Logs are full.

> > Follow up on: HELP! My logical logs are full. > This problem has actually kept our site from accepting the product. We started with 4.0, and have now gotten 4.1 from Informix as that was to have *fixed* the problem. Keep in mind that not backing up the logs and having a long transx aborted and fill up all the logs to a *deadlock* point are different subjects. The latter simply suspends things until you back up a log, the latter is deadly. (Hence, using contiguous backup for logs is not an optimum solution.) Although the *fix* was mentioned for 5.0 - it is there and undocumented in 4.1 via 2 new tbconfig parameters, LTXHWM and LTXEHWN. These are the percentages of all log space capacity at which a "long transaction" will be detected and aborted for rollback. It works okay, but if you use tbmonitor it will erase the new parameters from tbconfig, so be aware of that. The defaults for 4.0 are 75 and 100, respectively, meaning that a transaction is determined to be "long" if, say, 3 of 4 logs are being held (and are full) because of it. We set ours down to 50. The second parameter controls at what percentage should that one transactions get exclusive use of the log. Obviously, 100 does you no good at all... Hope this is of some help to you.... Scott Ford, DBA | sford@wvus.org | World Vision USA/ISD | elroy.jpl.nasa.gov!wvus!sford ___|___ 919 W. Huntingon Dr. | Voice: 818/357-1111 x3333 | Monrovia, CA 91016 | FAX: 818/303-6212 | |