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

Len Charest wrote: > > 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? I know of no other ways. I prefer to enlarge the log spaces because that does not force you to contort your application. And you obviously need the log space; this is no time to get chincy on disk space! That said, I would also mention that I have seen many flawed apps that issue a BEGIN WORK (or, for mode ANSI databases, just get started) but never issue a COMMIT until the end of the program, despite the logically separate operations that should be in their own separate transactions. If this is the your case you really should "replan" (who's making up words here? ;-) your apps and visibly separate the transactions. > Can LOCK TABLE inside of a transaction be of help? Not at all. It might keep you from running out of locks, another potential problem in a large transaction. But it has nothing to do with the number of log records written while trying to do all that work. -- -- Jake (Retrospectively realizes there is no future in hindsight) +------------------------------------------------------------+ | The expedient performance of a task with excessive concern | | regarding its duration-to-completion engenders a virtual | | certainty of diminished benefit therefrom. | | -- Benjamin Franklin (but he said it in 3 words) | +------------------------------------------------------------+