Re: Problem with long transactions

Bharat Shah writes: >It seems that you are running 4.00 version of OnLine. >Only solutions are: >1. Reduce the size of your transactions >2. Provide larger Logical log space Note that you do not want to just add logs, but rather make the logs BIGGER. The reason is that, with 4.0, the equiv of the long transaction high water mark (LTXHWM) is entering the last available log. If you simply add logs to a system with relatively small logs, you could actually make an LTX hang more likely. If the offending xaction is such that it is likely to fill up the logs, and you don't add enough for the worst case scenario, then rolling back (at LTX time) that xaction is more likely to fill that last log and hang your system. In 4.0, having fewer, large logs, while making it more likely that an LTX will happen, will make it less likely that rolling back the LTX will hang the system. The unfortunate aspect of resizing the logs is that it requires a complete reinit of your OnLine system. >3. Upgrade to 4.10+ versions & use HIGHWATER marks An upgrade to 4.10 (at least), if possible, is really a prudent move. 4.00, at this point, is bordering on ancient (could only happen in the software biz). >Whatever you choose to do, DO NOT KILL a sqlturbo process which is in >"X" state or you will trash your database. Very good advice. Dave -- Disclaimer: These opinions are not those of Informix Software, Inc. ************************************************************************** "I look back with some satisfaction on what an idiot I was when I was 25, but when I do that, I'm assuming I'm no longer an idiot." - Andy Rooney