RE: serial#, last_call_et for long running queries

  • From: "Chitale, Hemant K" <Hemant-K.Chitale@xxxxxx>
  • To: <ax.mount@xxxxxxxxx>
  • Date: Wed, 17 Sep 2014 10:57:55 +0800

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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] 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.

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 09-2014