Re: Help with "458: Long transaction aborted."

Setting LTXHWM to a higher value is dangerous to do. It just means that your transaction will continue a while longer before rolling back (and fill up more logical log space) and when it does actually roll back there might not be enough log space to do the roll back and the system will get stuck. The safest is to increase your logs and try again. Regards Dirk RG <rgriffin@farmerstel.com> wrote in article <01bdeff2$5afe9600$e44689d0@rgriffin>... > One other possible solution would be to modify LTXHWM to a larger value, > but this could cause other problems, and does require a bounce of the > engine. Your best bet is to add some logical logs. This would be both the > easiest and safest way, without modifying code. > -- > Regards, > Robert > > Len Charest <len@cogent.net> wrote in article <36143424.6C2A@cogent.net>... > > Hi- > > > > Is it possible to avoid the dreaded "458: Long transaction aborted." > > error without taking either of the actions recomended by the finderr > > docs, namely "replan [the app] so that it modifies fewer rows per > > transaction" or increase number/size of logical logs? > > > > Can LOCK TABLE inside of a transaction be of help? > > > > Thanks, > > -- > > Len Charest len@cogent.net > > Senior Software Engineer 888-4-COGENT > > Cogent Software, Inc. http://www.cogent.net/ > > >