Hi,
We found a session with a badly designed query, but somehow we missed to save
that session's information (got using "onstat -g ses <sid>"). We know the log
range when that query was running. Here is some information we got from
message log:
16:06:34 Aborting Long Transaction: tx: 0x114fc63b0 username: app uid: 117
How can we get the query text from archived logs, if we know above information.
regards,
Kamran
↪ replying to KAMRAN HAQ
You cannot get the query from the logs. The results of the query are
included, only. You MIGHT be able to infer that a particular table was
being updated to or deleted from and you may guess what the WHERE clause
contained, but see the actual INSERT, DELETE, or UPDATE statement? No.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Tue, Feb 8, 2011 at 9:05 PM, KAMRAN HAQ <khaq@i2cinc.com> wrote:
> Hi,
> We found a session with a badly designed query, but somehow we missed to
> save
> that session's information (got using "onstat -g ses <sid>"). We know the
> log
> range when that query was running. Here is some information we got from
> message log:
> 16:06:34 Aborting Long Transaction: tx: 0x114fc63b0 username: app uid: 117
> How can we get the query text from archived logs, if we know above
> information.
> regards,
> Kamran
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--0015175cdbfc974d62049bcffc41