Subject Ackward trace information
Author Anderson Farias
Hi all,

I'm analising some trace files (fb 2.5 audit) and can't understand some ocurrences. Sometimes it reports the 'statement finish' twice, the second one, with FAILED.

So, when this happens, did the statement failed or not? And, what may have happened?


Example:


2010-09-16T09:45:03.5150 (4724:0101E01C) EXECUTE_STATEMENT_FINISH
sig (ATT_230, SYSDBA:NONE, ISO88591, TCPv4:192.168.1.107)
D:\Estoque.exe:304
(TRA_15750, READ_COMMITTED | REC_VERSION | NOWAIT | READ_WRITE)

Statement 3053:
------------------------------------------------------
SELECT * FROM CONFIGURACOES

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PLAN (CONFIGURACOES NATURAL)
1968 records fetched
38 ms, 47 read(s), 4031 fetch(es)


2010-09-16T09:45:03.5460 (4724:0101E01C) FAILED EXECUTE_STATEMENT_FINISH
sig (ATT_230, SYSDBA:NONE, ISO88591, TCPv4:192.168.1.107)
D:\Estoque.exe:304
(TRA_15750, READ_COMMITTED | REC_VERSION | NOWAIT | READ_WRITE)

Statement 3053:
------------------------------------------------------
SELECT * FROM CONFIGURACOES

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PLAN (CONFIGURACOES NATURAL)
0 records fetched
0 ms


Thanks,
Anderson