RE: serial#, last_call_et for long running queries
Date: Wed, 17 Sep 2014 10:57:55 +0800
Message-ID: <0BDF2A25A09ADD40908745EEFC0A0FB602525F94_at_HKMGAXMB103A.zone1.scb.net>
SERIAL# goes together with SID as the unique identifier (within the instance) for a session.
You need to look at SEQ# to see if the Wait Event is changing.
Hemant K Chitale
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of amonte
Sent: Wednesday, September 17, 2014 1:51 AM
To: Oracle-L Group
Subject: serial#, last_call_et for long running queries
Hello
In order to identify long running queries I have been using last_call_et, if a session with a large last_call_et then it has not changed query.
Is it more useful add serial#? Since serial# does not change in a long running query neither?
Thank you
Alex
This email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please delete all copies and notify the sender immediately. You may wish to refer to the incorporation details of Standard Chartered PLC, Standard Chartered Bank and their subsidiaries at https://www.sc.com/en/incorporation-details.html.
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Sep 17 2014 - 04:57:55 CEST