Long Transaction Aborted
Simon Leigh asked what database setting causes a Long Transaction Aborted error. Yuri Dovgart said it happens when one transaction uses more of the logical logs than the LTXHWM percentage; increase the number or size of logs. Bruce Robertson warned that on his OnLine 5 site, with a 40% mark, filling all logs needed Informix support. Yuri advised leaving the defaults (50/60) and gave point-in-time restore as a way out.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Apparently this is caused by an incorrect setting in the database can anyone tell me what it is?? Thanks Simon
In article <7lv6fs$e89$1@uranium.btinternet.com>, "Simon Leigh" <simon.leigh@btinternet.com> wrote: > Apparently this is caused by an incorrect setting in the database > can anyone tell me what it is?? Percentage of logical logs occupied by the single transaction exceeds the number in the LTXHWM param. Increase number or size of your logical logs, if this happened frequently. -- With best regards, Yuri Dovgart, SAP R/3, Informix consultant, "Telecominvest" company. E-mail y_dovgart@tci.ukrtel.net Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.
But increase it too much and you could have problems. Onour site we have a high water mark of 40%. So if the transaction uses more than 40% of logical log space then you get long transaction aborted. If it is too high and all the logs get filled it requires someone from Informix to dial in and fix it ( Well on our Infx Online 5 anyway ). Yuri Dovgart <y_dovgart@tci.ukrtel.net> wrote in message news:7lvb3j$9df$1@nnrp1.deja.com... > In article <7lv6fs$e89$1@uranium.btinternet.com>, > "Simon Leigh" <simon.leigh@btinternet.com> wrote: > > Apparently this is caused by an incorrect setting in the database > > can anyone tell me what it is?? > > Percentage of logical logs occupied by the single transaction exceeds > the number in the LTXHWM param. Increase number or size of your logical > logs, if this happened frequently. > > -- > With best regards, Yuri Dovgart, > SAP R/3, Informix consultant, > "Telecominvest" company. > E-mail y_dovgart@tci.ukrtel.net > > > Sent via Deja.com http://www.deja.com/ > Share what you know. Learn what you don't. >
In article <7lvlrp$hbo$2@uranium.btinternet.com>, "Bruce Robertson" <br@leith.walk.co.uk> wrote: > But increase it too much and you could have problems. > Onour site we have a high water mark of 40%. So if the transaction uses more > than 40% of logical log space then you get long transaction aborted. If it > is too high and all the logs get filled it requires someone from Informix to > dial in and fix it ( Well on our Infx Online 5 anyway ). Bruce, I mean increase logs SIZE or logs NUMBER, not LTXHWM. Increasing number or size of your logs will give you ability to have bigger transactions with same LTXHWM. About values of LTXHWM and LTXEHWM - Informix told, that with default values (50 and 60 respectively) you will never find yourself in situation, when your system hangs because of no log space. Even if you in this trap - just do point-in-time restore according to the begin time of the long transaction, or restore without logical recovery. There are some scenarious - I can tell you through email, if you want me to. -- With best regards, Yuri Dovgart, SAP R/3, Informix consultant, "Telecominvest" company. E-mail y_dovgart@tci.ukrtel.net Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.