Cause of long transaction?

RS6000 IDS 7.31UC7 AIX 4.3.3. How do I determine(trap) who/what caused a long transaction?

Hi, you can see from the message that's written to the message log file (online.log), which session caused the LTX (long transaction). With that Session ID you can do "onstat -g ses <ses id>" or "onstat -g sql <ses id>" to find out, what the session is doing at the time, i.e. which SQL statement it is executing. Of course after the LTX has been rolled back or the session is closed, the info is gone ... To automate the process, you can add functionality to the ALARMPROGRAM (see $ONCONFIG file) or write your own alarmprogram. Class ID 22 denotes "LTX detected", so you can let the alarmprogram do the above onstat-commands and write the output to a file, send e-mail or take further actions ... Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions "Meza, Silvana" <smeza@fheg.follett.com> Sent by: forum.subscriber@iiug.org 17.02.2003 21:56 To: ids@iiug.org cc: Subject: Cause of long transaction? [416] RS6000 IDS 7.31UC7 AIX 4.3.3. How do I determine(trap) who/what caused a long transaction?

Hi, see "IBM Informix Administrator's Reference" Manual (for 9.3). Appendix C "Event Alarms" contains all the info about Class IDs of events, severity codes, example programs, etc. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions NormaJean.Sebastian@tellabs.com 21.02.2003 15:20 To: Martin Fuerderer/Germany/IBM@IBMDE cc: Subject: RE: Cause of long transaction? [424] Hi Martin, would you happen to know what Alarmprogram class is used for a lock overflow event and/or a 'VSEG added' event? is there a list of the alarm numbers somewhere? thanks, Norma Jean -----Original Message----- From: MARTINFU@de.ibm.com [mailto:MARTINFU@de.ibm.com] Sent: Wednesday, February 19, 2003 4:32 AM To: ids@iiug.org; forum.subscriber@iiug.org Subject: Re: Cause of long transaction? [424] Hi, you can see from the message that's written to the message log file (online.log), which session caused the LTX (long transaction). With that Session ID you can do "onstat -g ses <ses id>" or "onstat -g sql <ses id>" to find out, what the session is doing at the time, i.e. which SQL statement it is executing. Of course after the LTX has been rolled back or the session is closed, the info is gone ... To automate the process, you can add functionality to the ALARMPROGRAM (see $ONCONFIG file) or write your own alarmprogram. Class ID 22 denotes "LTX detected", so you can let the alarmprogram do the above onstat-commands and write the output to a file, send e-mail or take further actions ... Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions "Meza, Silvana" <smeza@fheg.follett.com> Sent by: forum.subscriber@iiug.org 17.02.2003 21:56 To: ids@iiug.org cc: Subject: Cause of long transaction? [416] RS6000 IDS 7.31UC7 AIX 4.3.3. How do I determine(trap) who/what caused a long transaction? ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================