Re: How can I find SQL statements causing deadlocks ?

In article <3289F4A7.3EAC@novadata.de>, Daniel Sarbacher <daniel.sarbacher@novadata.de> writes >Hello, > >I have got the following problem: >A deadlock in a multi-session-environment, several processes are working >parallel on the database, each process equals to one database session. >Informix error -243 / ISAM error -143 (Deadlock) while a SQL update >request. > >My configuration: Informix ONLINE 7.12 / AIX 4.1.4 / C++ programs with >embedded SQL. > >How can I find out which SQL statements in which process(es)/session(s) >caused the deadlock ? > You can't, one just gets rollback and the other succeeded. >Is there a way to trace all SQL statements (including start and stop >transaction statements) in a serialized form, ordered by time, over all >active processes/sessions ? There is no documented method. >Is there a possibillity to extend the output produced by 'SET EXPLAIN >ON' statement by time of execution, session-/process-id and signature of >transaction start/end ? > No. >Your comments and suggestions are welcomed and will be greatly >appreciated. > >Thank you, > >Jens > >----------------------------------------------------------------------- > >Jens Dennig >phone: 0049-7248-73-305 >email: jens.dennig@novadata.de >nova data AG >Becker - G'ring - Str. 26 >76307 Karslbad - Ittersbach >Germany -- David Williams