Skip to content

find current effective hidden param

find current effective hidden param published on Комментариев к записи find current effective hidden param нет
col PARAMETER format a20
col SESSION_VALUE format a20
col INSTANCE_VALUE format a20
col DEFAULT_VALUE format a20
col DESCRIPTION format a100
select a.ksppinm as Parameter,
b.ksppstvl Session_Value, 
c.ksppstvl Instance_Value ,
b.ksppstdf Default_value,
decode(bitand(a.ksppiflg/256,3),1, 'True', 'False') SESSMOD,
decode(bitand(a.ksppiflg/65536,3),1,'IMMEDIATE',2,'DEFERRED',3,'IMMEDIATE','FALSE') SYSMOD,
a.ksppdesc Description 
from sys.x$ksppi a, sys.x$ksppcv b , sys.x$ksppsv c where a.indx = b.indx and a.indx = c.indx
and REGEXP_LIKE (ksppinm, '^\_[^\_]')
and lower(b.ksppstdf) !='true' 
order by a.ksppinm;

script to analyze partition tables data distribution

script to analyze partition tables data distribution published on Комментариев к записи script to analyze partition tables data distribution нет
select table_owner||'.'||table_name,partition_name,100* (round (num_rows/ case when
        sum(num_rows) over( partition by table_name) >0 then sum(num_rows) over( partition by table_name)
        else 1
        end        
        ,3)) as pct_of_rows
        ,num_rows, sum(num_rows) over( partition by table_name)  total_row_cnt
        from dba_tab_partitions
    where table_name in 
    ( select table_name from DBA_PART_TABLES dpt where dpt.owner not like 'SYS%' and dpt.interval is null  and dpt.partitioning_type like '%RANGE%' ) 
order by 1,3 desc nulls last;

TABLE_NAME                               | PARTITION_NAME                 | PCT_OF_ROWS |   NUM_ROWS | TOTAL_ROW_CNT
---------------------------------------- | ------------------------------ | ----------- | ---------- | -------------
XXXX.OPN_HIS                             | P_MAX                          |         100 |   63308846 |      63309145
XXXX.OPN_HIS                             | P_2012_09                      |           0 |          2 |      63309145 
XXXX.OPN_HIS                             | P_2012_10                      |           0 |        297 |      63309145
XXXX.OPN_HIS                             | P_2012_08                      | <NULL>      | <NULL>     |      63309145

disk latency from ash by time

disk latency from ash by time published on 1 комментарий к записи disk latency from ash by time

some queryes to measure disk io

 select 100*(round ( count (*)/sum(count(*)) over(),2 )) as pct ,nvl(wait_class,'CPU') wait_class from v$active_session_history group by wait_class order by 1 desc;
 select 100*(round ( count (*)/sum(count(*)) over(),2 )) as pct ,nvl(event,'CPU') event from v$active_session_history where wait_class like '%I/O%' group by event order by 1 desc; 

generate pivot list

 select listagg( ''''||event||'''',',') within group (order by event )from v$active_session_history where wait_class like '%I/O%' group by event ;

or top wait pivot list:

with disk_events as  (
  select 100*(round ( count (*)/sum(count(*)) over(),2 )) as pct ,nvl(event,'CPU') event from v$active_session_history where wait_class like '%I/O%' group by event )
 select listagg( ''''||event||'''',',') within group (order by event )from disk_events where pct >5 ;

query and result

new:select * from
(select event,case when est_waits >0  
      then  round (est_dbtime_ms / est_waits,1)
              
                else null
                end
  as est_avg_latency_ms,
    time#
from ( 
      select event,
        round(
              sum(
                    case when time_waited >0 
                    then greatest(1,1000000/time_waited) 
                            else 0 end )
            ) as est_waits,
      sum(1000) as est_dbtime_ms ,
 TRUNC( ash.SAMPLE_TIME, 'MI') - mod( EXTRACT(minute FROM  ash.SAMPLE_TIME), 5) /(24 * 60) time#
from v$active_session_history ash 
  where ash.wait_class ='User I/O' 
      group by TRUNC(SAMPLE_TIME, 'MI') - mod( EXTRACT(minute FROM SAMPLE_TIME), 5) /(24 * 60) ,event 
      )    )
 pivot ( sum(est_avg_latency_ms) for event in (
 'db file scattered read','db file sequential read','log file parallel write')
 ) order by time#

TIME#               |                'db file scattered read' |               'db file sequential read' |               'log file parallel write'
------------------- | --------------------------------------- | --------------------------------------- | ---------------------------------------
10.08.2015 14.10.00 |                                     2,2 |                                      ,3 |                                  <NULL>
10.08.2015 14.15.00 |                                     2,4 |                                      ,2 |                                  <NULL>
10.08.2015 14.20.00 |                                     1,7 |                                      ,3 |                                  <NULL>
10.08.2015 14.25.00 |                                     1,3 |                                      ,3 |                                  <NULL>
10.08.2015 14.30.00 |                                     3,5 |                                      ,2 |                                  <NULL>
10.08.2015 14.35.00 |                                     1,8 |                                      ,3 |                                  <NULL>
10.08.2015 14.40.00 |                                     1,1 |                                      ,3 |                                  <NULL>
10.08.2015 14.45.00 |                                     2,6 |                                      ,2 |                                  <NULL>
10.08.2015 14.50.00 |                                     1,5 |                                      ,3 |                                  <NULL>
10.08.2015 14.55.00 |                                     1,2 |                                      ,3 |                                  <NULL>
10.08.2015 15.00.00 |                                     2,6 |                                      ,2 |                                  <NULL>
10.08.2015 15.05.00 |                                     1,3 |                                      ,4 |                                  <NULL>
10.08.2015 15.10.00 |                                     1,6 |                                      ,3 |                                  <NULL>
10.08.2015 15.15.00 |                                       3 |                                      ,2 |                                  <NULL>
10.08.2015 15.20.00 |                                     1,4 |                                      ,3 |                                  <NULL>
10.08.2015 15.25.00 |                                     1,6 |                                      ,3 |                                  <NULL>
10.08.2015 15.30.00 |                                     3,1 |                                      ,2 |                                  <NULL>
10.08.2015 15.35.00 |                                     1,8 |                                      ,4 |                                  <NULL>
10.08.2015 15.40.00 |                                     1,2 |                                      ,3 |                                  <NULL>
10.08.2015 15.45.00 |                                     2,5 |                                      ,2 |                                  <NULL>
10.08.2015 15.50.00 |                                     1,6 |                                      ,3 |                                  <NULL>
10.08.2015 15.55.00 |                                     1,4 |                                      ,3 |                                  <NULL>
10.08.2015 16.00.00 |                                     4,8 |                                      ,2 |                                  <NULL>
10.08.2015 16.05.00 |                                     1,8 |                                      ,4 |                                  <NULL>
10.08.2015 16.10.00 |                                     1,2 |                                      ,4 |                                  <NULL>
10.08.2015 16.15.00 |                                       3 |                                      ,2 |                                  <NULL>
10.08.2015 16.20.00 |                                     1,3 |                                      ,3 |                                  <NULL>
10.08.2015 16.25.00 |                                     1,1 |                                      ,3 |                                  <NULL>
10.08.2015 16.30.00 |                                     3,1 |                                      ,2 |                                  <NULL>
10.08.2015 16.35.00 |                                     1,6 |                                      ,3 |                                  <NULL>
10.08.2015 16.40.00 |                                     1,6 |                                      ,3 |                                  <NULL>
10.08.2015 16.45.00 |                                     2,9 |                                      ,2 |                                  <NULL>
10.08.2015 16.50.00 |                                     1,6 |                                      ,3 |                                  <NULL>
10.08.2015 16.55.00 |                                     1,3 |                                      ,2 |                                  <NULL>
10.08.2015 17.00.00 |                                     2,2 |                                      ,2 |                                  <NULL>
10.08.2015 17.05.00 |                                     1,5 |                                      ,4 |                                  <NULL>
10.08.2015 17.10.00 |                                     1,7 |                                      ,3 |                                  <NULL>
10.08.2015 17.15.00 |                                       3 |                                      ,2 |                                  <NULL>
10.08.2015 17.20.00 |                                     1,8 |                                      ,3 |                                  <NULL>
10.08.2015 17.25.00 |                                     1,3 |                                      ,3 |                                  <NULL>
10.08.2015 17.30.00 |                                     3,3 |                                      ,3 |                                  <NULL>
10.08.2015 17.35.00 |                                     1,6 |                                      ,3 |                                  <NULL>
10.08.2015 17.40.00 |                                      ,7 |                                      ,3 |                                  <NULL>

this output can be used to build graphs:

Снимок экрана 2015-08-10 в 17.38.43

awr report by hour

awr report by hour published on Комментариев к записи awr report by hour нет

simplest way to generate awr report by hour after benchmark
export awr

@?/rdbms/admin/awrextr.sql 

import awr

@?/rdbms/admin/awrload.sql

— make sure to set line size appropriately
— set linesize 152

generate awr

 set termout off
set linesize 80
set pagesize 10000
select 'spool awrrpt_dwhfrn_'|| snap_id ||'.html'|| chr(13)||
 'select output from table(dbms_workload_repository.awr_report_text('||dbid||',1,'||snap_id||','|| LEAD (snap_id, 1)  OVER (ORDER BY  dbid,snap_id ) ||',0));' || chr(13)||
 ' spool off '
 from dba_hist_snapshot where dbid !=1399642255 and extract( minute from begin_interval_time ) <2 ;

Oracle: latch: cache buffers chains

Oracle: latch: cache buffers chains published on Комментариев к записи Oracle: latch: cache buffers chains нет

save at my blog, original

Waits on the cache buffer chains latch, ie the wait event «latch: cache buffers chains» happen when there is extremely high and concurrent access to the same block in a database. Access to a block is normally a fast operation but if concurrent users access a block fast enough, repeatedly then simple access to the block can become an bottleneck. The most common occurance of cbc (cache buffer chains) latch contention happens when multiple users are running nest loop joins on a table and accessing the table driven into via an index. Since the NL join is basically a

  For all rows in i
     look up a value in j  where j.field1 = i.val
  end loop

then table j’s index on field1 will get hit for every row returned from i. Now if the lookup on i returns a lot of rows and if multiple users are running this same query then the index root block is going to get hammered on the index j(field1).

In order to solve a CBC latch bottleneck we need to know what SQL is causing the bottleneck and what table or index that the SQL statement is using is causing the bottleneck.

From ASH data this is fairly easy:

    select
          count(*),
          sql_id,
          nvl(o.object_name,ash.current_obj#) objn,
          substr(o.object_type,0,10) otype,
          CURRENT_FILE# fn,
          CURRENT_BLOCK# blockn
    from  v$active_session_history ash
        , all_objects o
    where event like 'latch: cache buffers chains'
      and o.object_id (+)= ash.CURRENT_OBJ#
    group by sql_id, current_obj#, current_file#,
                   current_block#, o.object_name,o.object_type
    order by count(*)
    /        

From the out put it looks like we have both the SQL (at least the id, we can get the text with the id) and the block:

    CNT SQL_ID        OBJN     OTYPE   FN BLOCKN
    ---- ------------- -------- ------ --- ------
      84 a09r4dwjpv01q MYDUAL   TABLE    1  93170

But the block actually is probably left over from a recent IO and not actually the CBC hot block though it might be.
We can investigate further to get more information by looking at P1, P2 and P3 for the CBC latch wait. How can we find out what P1, P2 and P3 mean? by looking them up in V$EVENT_NAME:

    select * from v$event_name
    where name = 'latch: cache buffers chains'

    EVENT#     NAME                         PARAMETER1 PARAMETER2 PARAMETER3
    ---------- ---------------------------- ---------- ---------- ----------
            58 latch: cache buffers chains     address     number      tries 

So P1 is the address of the latch for the cbc latch wait.
Now we can group the CBC latch waits by the address and find out what address had the most waits:

    select
        count(*),
        lpad(replace(to_char(p1,'XXXXXXXXX'),' ','0'),16,0) laddr
    from v$active_session_history
    where event='latch: cache buffers chains'
    group by p1
    order by count(*);

    COUNT(*)  LADDR
    ---------- ----------------
          4933 00000004D8108330   

 

In this case, there is only one address that we had waits for, so now we can look up what blocks (headers actually) were at that address

   select o.name, bh.dbarfil, bh.dbablk, bh.tch
    from x$bh bh, obj$ o
    where tch > 5
      and hladdr='00000004D8108330'
      and o.obj#=bh.obj
    order by tch

    NAME        DBARFIL DBABLK  TCH
    ----------- ------- ------ ----
    EMP_CLUSTER       4    394  120

We look for the block with the highest «TCH» or «touch count». Touch count is a count of the times the block has been accesses. The count has some restrictions. The count is only incremented once every 3 seconds, so even if I access the block 1 million times a second, the count will only go up once every 3 seconds. Also, and unfortunately, the count gets zeroed out if the block cycles through the buffer cache, but probably the most unfortunate is that this analysis only works when the problem is currently happening. Once the problem is over then the blocks will usually get pushed out of the buffer cache.

In the case where the CBC latch contention is happening right now we can run all of this analysis in one query

   select
            name, file#, dbablk, obj, tch, hladdr
    from x$bh bh
        , obj$ o
     where
           o.obj#(+)=bh.obj and
          hladdr in
    (
        select ltrim(to_char(p1,'XXXXXXXXXX') )
        from v$active_session_history
        where event like 'latch: cache buffers chains'
        group by p1
        having count(*) > 5
    )
       and tch > 5
    order by tch

example output

    NAME          FILE# DBABLK    OBJ TCH HLADDR
    ------------- ----- ------ ------ --- --------
    BBW_INDEX         1 110997  66051  17 6BD91180
    IDL_UB1$          1  54837     73  18 6BDB8A80
    VIEW$             1   6885     63  20 6BD91180
    VIEW$             1   6886     63  24 6BDB8A80
    DUAL              1   2082    258  32 6BDB8A80
    DUAL              1   2081    258  32 6BD91180
    MGMT_EMD_PING     3  26479  50312 272 6BDB8A80

This can be misleading, as TCH gets set to 0 every rap around the LRU and it only gets updated once every 3 seconds, so in this case DUAL was my problem table not MGMT_EMD_PING

Deeper Analysis from Tanel Poder

http://blog.tanelpoder.com/2009/08/27/latch-cache-buffers-chains-latch-contention-a-better-way-for-finding-the-hot-block/comment-page-1/#comment-2437

Using Tanel’s ideas here’s a script to get the objects that we have the most cbc latch waits on

    col object_name for a35
    col cnt for 99999

    SELECT
      cnt, object_name, object_type,file#, dbablk, obj, tch, hladdr
    FROM (
      select count(*) cnt, rfile, block from (
        SELECT /*+ ORDERED USE_NL(l.x$ksuprlat) */
          --l.laddr, u.laddr, u.laddrx, u.laddrr,
          dbms_utility.data_block_address_file(to_number(object,'XXXXXXXX')) rfile,
          dbms_utility.data_block_address_block(to_number(object,'XXXXXXXX')) block
        FROM
           (SELECT /*+ NO_MERGE */ 1 FROM DUAL CONNECT BY LEVEL <= 100000) s,
           (SELECT ksuprlnm LNAME, ksuprsid sid, ksuprlat laddr,
           TO_CHAR(ksulawhy,'XXXXXXXXXXXXXXXX') object
            FROM x$ksuprlat) l,
           (select  indx, kslednam from x$ksled ) e,
           (SELECT
                        indx
                      , ksusesqh     sqlhash
       , ksuseopc
       , ksusep1r laddr
                 FROM x$ksuse) u
        WHERE LOWER(l.Lname) LIKE LOWER('%cache buffers chains%')
         AND  u.laddr=l.laddr
         AND  u.ksuseopc=e.indx
         AND  e.kslednam like '%cache buffers chains%'
        )
       group by rfile, block
       ) objs,
         x$bh bh,
         dba_objects o
    WHERE
          bh.file#=objs.rfile
     and  bh.dbablk=objs.block
     and  o.object_id=bh.obj
    order by cnt
    ;

    CNT  OBJECT_NAME       TYPE  FILE#  DBABLK    OBJ   TCH  HLADDR
    ---- ----------------- ----- ----- ------- ------ ----- --------
       1 WB_RETROPAY_EARNS TABLE     4   18427  52701  1129 335F7C00
       1 WB_RETROPAY_EARNS TABLE     4   18194  52701  1130 335F7C00
       3 PS_RETROPAY_RQST  TABLE     4   13253  52689  1143 33656D00
       3 PS_RETROPAY_RQST  INDEX     4   13486  52692   997 33656D00
       3 WB_JOB            TABLE     4   14443  52698   338 335B9080
       5 PS_RETROPAY_RQST  TABLE     4   13020  52689   997 33656D00
       5 WB_JOB            TABLE     4   14676  52698   338 335B9080
       5 WB_JOB            TABLE     4   13856  52698   338 335F7C00
       6 WB_JOB            TABLE     4   13623  52698   338 335F7C00
       7 WB_JOB            TABLE     4   14909  52698   338 335B9080
     141 WB_JOB            TABLE     4   15142  52698   338 335B9080
    2513 WB_JOB            INDEX     4   13719  52699   997 33656D00

Why do we get cache buffers chains latch contention?

In order to understand why we get CBC latch contention we have to understand what the CBC latch protects. The CBC latch protects information controlling the buffer cache. Here is a schematic of computer memory and the Oracle processes, SGA and the main components of the SGA:

oracle_memory_processes

The buffer cache holds in memory versions of datablocks for faster access. Can you imagine though how we find a block we want in the buffer cache? The buffer cache doesn’t have a index of blocks it contains and we certainly don’t scan the whole cache looking for the block we want (though I have heard that as a concern when people increase the size of there buffer cache). The way we find a block in the buffer cache is by taking the block’s address, ie it’s file and block number and hashing it. What’s hashing? A simple example of hashing is the «Modulo» function

1 mod 4 = 1
2 mod 4 = 2
3 mod 4 = 3
4 mod 4 = 0
5 mod 4 = 1
6 mod 4 = 2
7 mod 4 = 3
8 mod 4 = 0

Using «mod 4» as a hash funtion creates 4 possible results. These results are used by Oracle as «buckets» or identifiers of locations to store things. The things in this case will be block headers.

buffer_cache_buckets

Block headers are meta data about data block including pointers to the actual datablock as well as pointers to the other headers in the same bucket.

buffer_cache_block_header x$BH

The block headers in the hash buckets are connected via a doubly linked list. One link points forward the other points backwards

buffer_cache_linked_lists_top

The resulting layout looks like

buffer_cache

the steps to find a block in the cache are

buffer_cache_steps_to_get_block

If there are a lot of sessions concurrently accessing the same buffer header (or buffer headers in the same bucket) then the latch that protects that bucket will get hot and users will have to wait getting «latch: cache buffers chains» wait.

buffer_cache_cbc_longchain

Two ways this can happen (among probably several others)

buffer_cache_cbc_two_cases

For the nested loops example, Oracle will in some (most?) cases try and pin the root block of the index because Oracle knows we will be using it over and over. When a block is pinned we don’t have to use the cbc latch. There seem to be cases (some I think might be bugs) where the root block doesn’t get pinned. (I want to look into this more — let me know if you have more info)

One thing that can make CBC latch contention worse is if a session is modifying the data block that users are reading because readers will clone a block with uncommitted changes and roll back the changes in the cloned block:

buffer_cache_cbc_consistent_read

all these clone copies will go in the same bucket and be protected by the same latch:

buffer_cache_cbc_contention

How many copies of a block are in the cache?

    select
           count(*)
         , name
         , file#
         , dbablk
         , hladdr
    from   x$bh bh
              , obj$ o
    where
          o.obj#(+)=bh.obj and
          hladdr in
    (
        select ltrim(to_char(p1,'XXXXXXXXXX') )
        from v$active_session_history
        where event like 'latch: cache%'
        group by p1
    )
    group by name,file#, dbablk, hladdr
    having count(*) > 1
    order by count(*);

    CNT NAME        FILE#  DBABLK HLADDR
    --- ---------- ------ ------- --------
     14 MYDUAL          1   93170 2C9F4B20

Notice that the number of copies, 14, is higher the the max number of copies allowed set by «_db_block_max_cr_dba = 6» in 10g. The reason is this value is just a directive not a restriction. Oracle tries to limit the number of copies.

Solutions

Find SQL ( Why is application hitting the block so hard? )
Possibly change application logic
Eliminate hot spots
Nested loops, possibly
Hash Partition the index with hot block
Use Hash Join instead of Nested loop join
Use Hash clusters
Look up tables (“select language from lang_table where …”)
Change application
Use plsql function
Spread data out to reduce contention, like set PCTFREE to 0 and recreate the table so that there is only one row per block
Select from dual
Possibly use x$dual
Note starting in 10g Oracle uses the «fast dual» table (ie x$dual) automatically when executing a query on dual as long as the column «dummy» is not accessed. Accessing dummy would be cases like
select count(*) from dual;
select * from dual;
select dummy from dual;
an example of not accessing «dummy» would be:
select 1 from dual;
select sysdate from dual;

Updates, inserts , select for update on blocks while reading those blocks
Cause multiple copies and make things worse

What would OEM do?

In DB Optimizer:

Other References
http://blog.tanelpoder.com/2009/08/27/latch-cache-buffers-chains-latch-contention-a-better-way-for-finding-the-hot-block
http://www.pythian.com/news/1135/tuning-latch-contention-cache-buffers-chain-latches/
http://www.oaktable.net/content/latch-cache-buffer-chains-small-index-primary-key-caused-concurrent-batch-scripts-select-sta#comment-6
http://jonathanlewis.wordpress.com/2008/02/09/index-rebuild-10g/

 

 

http://www.programering.com/a/MzNzkzMwATM.html

perf-tools linux

perf-tools linux published on Комментариев к записи perf-tools linux нет
perf-tools
looks awesome
example :
[root@nb-abushmelev perf-tools] # ./iosnoop -Q -ts -Qp 28951
Tracing block I/O issued by PID 28951. Ctrl-C to end.
STARTs          ENDs            COMM         PID    TYPE DEV      BLOCK        BYTES     LATms
439471.905014   439471.909309   ora_ckpt_orc 28951  WS   8,0      89272384     16384      4.29
439471.909341   439471.914798   ora_ckpt_orc 28951  WS   8,0      0            0          5.46
439471.914874   439471.914930   ora_ckpt_orc 28951  WS   8,0      99987520     16384      0.06
439471.914948   439471.918243   ora_ckpt_orc 28951  WS   8,0      0            0          3.30
439474.919898   439474.919962   ora_ckpt_orc 28951  WS   8,0      89272384     16384      0.06
439474.920002   439474.925042   ora_ckpt_orc 28951  WS   8,0      0            0          5.04
439474.925099   439474.925156   ora_ckpt_orc 28951  WS   8,0      99987520     16384      0.06
439474.925170   439474.927063   ora_ckpt_orc 28951  WS   8,0      0            0          1.89
439477.928636   439477.928700   ora_ckpt_orc 28951  WS   8,0      89272384     16384      0.06
439477.928717   439477.932240   ora_ckpt_orc 28951  WS   8,0      0            0          3.52
439477.932309   439477.932365   ora_ckpt_orc 28951  WS   8,0      99987520     16384      0.06
439477.932391   439477.934258   ora_ckpt_orc 28951  WS   8,0      0            0          1.87

Query optimization:

Query optimization: published on Комментариев к записи Query optimization: нет

awr_top2 script

18:44:12 (3)system@some_database> @awr_top2

 In |               |                |                                |     Top |        | Samp |       |   Wai |  User |  Sys |      |      |   Con |       |      |
 st | Time          | Top SQL        | Top event                      | blocker |    AAS |  les |   CPU |    ts |    IO |   IO | Conf |  Net |   cur |   App | LGWR |  RAC
--- | ------------- | -------------- | ------------------------------ | ------- | ------ | ---- | ----- | ----- | ----- | ---- | ---- | ---- | ----- | ----- | ---- | ----
  1 | 16-JUN 18:14  | c9p3ns1cusnmx  | ON CPU                         |     570 |    1.5 |   40 |    56 |     4 |     5 |    3 |    0 |    0 |     0 |     0 |    2 |    3
    | 16-JUN 18:15  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.3 |   59 |    74 |     4 |     3 |    4 |    0 |    0 |     0 |     0 |    4 |    0
    | 16-JUN 18:16  | 3fp6nwg71dbna  | ON CPU                         | <NULL>  |    1.7 |   60 |   101 |     0 |     0 |    0 |    0 |    0 |     1 |     0 |    0 |    0
    | 16-JUN 18:17  | 3fp6nwg71dbna  | ON CPU                         | <NULL>  |    1.2 |   60 |    74 |     0 |     0 |    1 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:18  | c9p3ns1cusnmx  | ON CPU                         | <NULL>  |    1.3 |   60 |    75 |     3 |     2 |    1 |    0 |    1 |     0 |     0 |    0 |    1
    | 16-JUN 18:19  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.8 |   60 |   102 |     4 |     1 |    2 |    0 |    0 |     0 |     0 |    2 |    1
    | 16-JUN 18:20  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.3 |   60 |    75 |     2 |     0 |    5 |    0 |    0 |     0 |     0 |    2 |    0
    | 16-JUN 18:21  | <NULL>         | ON CPU                         | <NULL>  |    1.0 |   60 |    61 |     0 |     0 |    0 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:22  | 3fp6nwg71dbna  | ON CPU                         | <NULL>  |    1.7 |   60 |    95 |     4 |     1 |    4 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:23  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.5 |   59 |    87 |     3 |     0 |    3 |    0 |    0 |     0 |     0 |    2 |    0
    | 16-JUN 18:24  | f711myt0q6cma  | ON CPU                         |     570 |    1.1 |   60 |    64 |     1 |     0 |    2 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:25  | 3fp6nwg71dbna  | ON CPU                         | <NULL>  |    1.2 |   60 |    72 |     0 |     0 |    0 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:26  | 3fp6nwg71dbna  | ON CPU                         | <NULL>  |    1.6 |   60 |    92 |     1 |     0 |    2 |    0 |    0 |     0 |     0 |    0 |    1
    | 16-JUN 18:27  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.5 |   60 |    78 |     9 |     1 |    8 |    0 |    0 |     0 |     0 |    2 |    1
    | 16-JUN 18:28  | gjfr89gj2ngfu  | ON CPU                         |     570 |    1.1 |   60 |    62 |     5 |     1 |    5 |    0 |    0 |     0 |     0 |    2 |    0
    | 16-JUN 18:29  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.3 |   60 |    77 |     3 |     0 |    6 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:30  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.4 |   59 |    80 |     2 |     0 |    2 |    0 |    0 |     0 |     0 |    2 |    1
    | 16-JUN 18:31  | dqrrfrf2d0h8q  | ON CPU                         | <NULL>  |    1.0 |   60 |    62 |     0 |     0 |    2 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:32  | f1y8kbhh6v9sv  | ON CPU                         |     570 |    1.2 |   60 |    69 |     1 |     0 |    2 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:33  | c9p3ns1cusnmx  | ON CPU                         |     570 |    1.4 |   60 |    75 |    10 |     3 |    5 |    0 |    0 |     0 |     0 |    4 |    2
    | 16-JUN 18:34  | cwd64da6cnm9j  | ON CPU                         | <NULL>  |    1.1 |   60 |    64 |     3 |     0 |    2 |    0 |    0 |     0 |     0 |    2 |    0
    | 16-JUN 18:35  | cwd64da6cnm9j  | ON CPU                         |     570 |    1.2 |   60 |    65 |     9 |     1 |    4 |    0 |    0 |     0 |     0 |    9 |    0
    | 16-JUN 18:36  | 5s7umwd3ppb7w  | ON CPU                         |     789 |    1.9 |   60 |    95 |    19 |     2 |    1 |    0 |    0 |     0 |     0 |    1 |   15
    | 16-JUN 18:37  | c9p3ns1cusnmx  | ON CPU                         |     570 |    1.2 |   59 |    67 |     3 |     1 |    1 |    0 |    0 |     0 |     0 |    2 |    2
    | 16-JUN 18:38  | d56fs2a7v6rkq  | ON CPU                         |     570 |    1.1 |   60 |    64 |     1 |     0 |    3 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:39  | <NULL>         | ON CPU                         |     570 |    1.0 |   60 |    61 |     1 |     0 |    3 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:40  | c9p3ns1cusnmx  | ON CPU                         | <NULL>  |    1.4 |   60 |    82 |     3 |     1 |    2 |    0 |    0 |     0 |     0 |    0 |    2
    | 16-JUN 18:41  | c9p3ns1cusnmx  | ON CPU                         |     570 |    1.2 |   60 |    66 |     5 |     0 |    5 |    0 |    0 |     0 |     0 |    3 |    1
    | 16-JUN 18:42  | 3fp6nwg71dbna  | ON CPU                         |     570 |    1.5 |   60 |    78 |    14 |     0 |   10 |    0 |    0 |     0 |     0 |   10 |    4
    | 16-JUN 18:43  | c9p3ns1cusnmx  | ON CPU                         |     570 |    1.1 |   60 |    63 |     3 |     0 |    7 |    0 |    0 |     0 |     0 |    3 |    0
    | 16-JUN 18:44  | c9p3ns1cusnmx  | ON CPU                         |     570 |    1.5 |   21 |    26 |     6 |     0 |    5 |    0 |    0 |     1 |     0 |    2 |    2

  3 | 16-JUN 18:14  | d3tcbyxaa65ku  | ON CPU                         | <NULL>  |    5.3 |   40 |   188 |    24 |    23 |    1 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:15  | d3tcbyxaa65ku  | ON CPU                         | <NULL>  |    1.8 |   60 |    98 |    12 |    15 |    0 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:16  | f5b45ajkg4rdd  | enq: TA - contention           |     854 |     .3 |   59 |    18 |     1 |     0 |    2 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:17  | d3tcbyxaa65ku  | direct path read               |     570 |    2.3 |   60 |    81 |    59 |    52 |    2 |    0 |    0 |     0 |     0 |    4 |    1
    | 16-JUN 18:18  | d3tcbyxaa65ku  | ON CPU                         |     854 |    3.2 |   60 |   145 |    48 |    44 |    2 |    0 |    0 |     0 |     0 |    2 |    0
    | 16-JUN 18:19  | d3tcbyxaa65ku  | ON CPU                         |     854 |    3.9 |   59 |   209 |    21 |    20 |    1 |    0 |    0 |     0 |     0 |    0 |    1
    | 16-JUN 18:20  | d3tcbyxaa65ku  | ON CPU                         |     570 |    4.5 |   60 |   222 |    46 |    44 |    6 |    0 |    0 |     0 |     0 |    2 |    0
    | 16-JUN 18:21  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.6 |   60 |   245 |    30 |    30 |    0 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:22  | d3tcbyxaa65ku  | ON CPU                         |     570 |    4.7 |   60 |   249 |    33 |    26 |    6 |    0 |    0 |     0 |     0 |    5 |    1
    | 16-JUN 18:23  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.2 |   60 |   178 |    71 |    69 |    2 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:24  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.7 |   60 |   231 |    53 |    50 |    2 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:25  | d3tcbyxaa65ku  | ON CPU                         | <NULL>  |    4.4 |   60 |   227 |    34 |    31 |    1 |    0 |    0 |     0 |     0 |    0 |    3
    | 16-JUN 18:26  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.5 |   59 |   228 |    37 |    36 |    2 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:27  | d3tcbyxaa65ku  | ON CPU                         |     570 |    4.7 |   60 |   229 |    50 |    47 |    4 |    0 |    0 |     0 |     0 |    3 |    0
    | 16-JUN 18:28  | d3tcbyxaa65ku  | ON CPU                         | <NULL>  |    4.6 |   60 |   250 |    25 |    24 |    1 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:29  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.7 |   60 |   242 |    37 |    32 |    3 |    0 |    0 |     0 |     0 |    3 |    2
    | 16-JUN 18:30  | d3tcbyxaa65ku  | ON CPU                         |     570 |    4.4 |   60 |   219 |    45 |    45 |    3 |    0 |    0 |     0 |     0 |    2 |    0
    | 16-JUN 18:31  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.8 |   60 |   259 |    27 |    26 |    0 |    0 |    0 |     0 |     0 |    0 |    1
    | 16-JUN 18:32  | d3tcbyxaa65ku  | ON CPU                         | <NULL>  |    4.9 |   60 |   249 |    44 |    43 |    0 |    0 |    0 |     0 |     0 |    0 |    1
    | 16-JUN 18:33  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.7 |   60 |   257 |    27 |    26 |    0 |    0 |    0 |     0 |     0 |    0 |    1
    | 16-JUN 18:34  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.7 |   59 |   236 |    42 |    41 |    4 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:35  | d3tcbyxaa65ku  | ON CPU                         |     570 |    4.8 |   60 |   221 |    68 |    63 |    4 |    0 |    0 |     0 |     0 |    1 |    4
    | 16-JUN 18:36  | d3tcbyxaa65ku  | ON CPU                         |     854 |    5.5 |   60 |   280 |    47 |    42 |    1 |    0 |    0 |     0 |     0 |    0 |    4
    | 16-JUN 18:37  | d3tcbyxaa65ku  | ON CPU                         | <NULL>  |    4.7 |   60 |   257 |    24 |    24 |    2 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:38  | d3tcbyxaa65ku  | ON CPU                         | <NULL>  |    4.5 |   60 |   244 |    26 |    26 |    0 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:39  | d3tcbyxaa65ku  | ON CPU                         |     854 |    5.1 |   60 |   267 |    37 |    36 |    3 |    0 |    0 |     0 |     0 |    1 |    0
    | 16-JUN 18:40  | d3tcbyxaa65ku  | ON CPU                         |     570 |    4.9 |   60 |   247 |    45 |    41 |    3 |    0 |    0 |     0 |     0 |    1 |    1
    | 16-JUN 18:41  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.6 |   59 |   244 |    29 |    26 |    2 |    0 |    0 |     0 |     0 |    0 |    0
    | 16-JUN 18:42  | d3tcbyxaa65ku  | ON CPU                         |     570 |    4.4 |   60 |   196 |    69 |    56 |   16 |    0 |    0 |     0 |     0 |   10 |    2
    | 16-JUN 18:43  | d3tcbyxaa65ku  | ON CPU                         |     570 |    5.5 |   60 |   260 |    72 |    60 |   10 |    0 |    0 |     1 |     0 |    6 |    4
    | 16-JUN 18:44  | d3tcbyxaa65ku  | ON CPU                         |     854 |    4.9 |   21 |    85 |    17 |    16 |    1 |    0 |    0 |     0 |     0 |    1 |    0


62 rows selected.
18:46:33 (3)system@some_database> @plan_id d3tcbyxaa65ku

SQL_ID  d3tcbyxaa65ku, child number 2
-------------------------------------
select * from ( select row_.*, rownum rownum_ from ( select this_.id as
y0_, this_.status as y1_, this_.service as y2_, this_.request_date as
y3_, this_.response_timestamp as y4_, substr(this_.response_content, 0,
5) responseContent, this_.labels as y6_, this_.sign_subj as y7_,
this_.sign_org as y8_, this_.author as y9_ from SOME_TABLE
this_ left outer join SOME_TABLE2 authoruser1_ on
this_.author=authoruser1_.id where ((this_.author is null or
this_.author=:1  or authoruser1_.owner=:2  or this_.author in (select
user_.id as y0_ from SOME_TABLE2 user_ where user_.region=:3 )) and
this_.author is not null and this_.service in (:4 , :5 , :6 , :7 , :8 ,
:9 , :10 , :11 , :12 , :13 , :14 , :15 , :16 , :17 , :18 , :19 , :20 ,
:21 , :22 , :23 , :24 , :25 , :26 , :27 , :28 , :29 , :30 , :31 , :32 ,
:33 , :34 , :35 , :36 , :37 , :38 , :39 , :40 , :41 , :42 , :43 , :44 ,
:45 , :46 , :47 , :48 , :49 , :50 , :51 , :52 , :53 , :54 , :55 , :56 ,
:57 , :58 , :59 , :60 , :61 , :62 , :63 , :64 , :6


Plan hash value: 1496851868

-------------------------------------------------------------------------------------------------
| Id  | Operation                        | Name                           | E-Rows | Cost (%CPU)|
-------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                 |                                |        |    79 (100)|
|*  1 |  VIEW                            |                                |      2 |    79   (0)|
|*  2 |   COUNT STOPKEY                  |                                |        |            |
|   3 |    VIEW                          |                                |      2 |    79   (0)|
|*  4 |     FILTER                       |                                |        |            |
|   5 |      NESTED LOOPS OUTER          |                                |      2 |    79   (0)|
|*  6 |       TABLE ACCESS BY INDEX ROWID| SOME_TABLE                     |      2 |    77   (0)|
|   7 |        INDEX FULL SCAN DESCENDING| SOME_TABLE_REDIF_IDX           |    574K|     3   (0)|
|   8 |       TABLE ACCESS BY INDEX ROWID| SOME_TABLE2                    |      1 |     1   (0)|
|*  9 |        INDEX UNIQUE SCAN         | SYS_C00288211                  |      1 |     0   (0)|
|* 10 |      TABLE ACCESS BY INDEX ROWID | SOME_TABLE2                    |      1 |     2   (0)|
|* 11 |       INDEX UNIQUE SCAN          | SYS_C00288211                  |      1 |     1   (0)|
-------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter("ROWNUM_">:199)
   2 - filter(ROWNUM<=:198)
   4 - filter(("SYS_ALIAS_1"."AUTHOR"=:1 OR "AUTHORUSER1_"."OWNER"=:2 OR  IS NOT NULL))
   6 - filter(("SYS_ALIAS_1"."AUTHOR" IS NOT NULL AND
              SYS_EXTRACT_UTC("LAST_UPDATED")>SYS_EXTRACT_UTC(:197) AND
              INTERNAL_FUNCTION("SYS_ALIAS_1"."SERVICE") AND "SYS_ALIAS_1"."PGU_CONV_ID" IS NULL))
   9 - access("SYS_ALIAS_1"."AUTHOR"="AUTHORUSER1_"."ID")
  10 - filter("USER_"."REGION"=:3)
  11 - access("USER_"."ID"=:B1)

 (3)system@some_database> l
  1* select * from table (dbms_xplan.display_cursor('&1',NULL,'ALLSTATS PREDICATE COST LAST +ALLSTATS' ))
18:44:21 (3)system@some_database> @http://blog.tanelpoder.com/files/scripts/sqlid.sql d3tcbyxaa65ku % %
Show SQL text, child cursors and execution stats for SQLID d3tcbyxaa65ku child %
old   9:        sql_id = ('&1')
new   9:        sql_id = ('d3tcbyxaa65ku')
old  10: and child_number like '&2'
new  10: and child_number like '%'

HASH_VALUE | PLAN_HASH_VALUE |  CH# | SQL_TEXT
---------- | --------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------
1419974234 |      1496851868 |    2 | select * from ( select row_.*, rownum rownum_ from ( select this_.id as y0_, this_.status as y1_, this_.service as y2_, this_.request_date as y3_,
           |                 |      | this_.response_timestamp as y4_, substr(this_.response_content, 0, 5) responseContent, this_.labels as y6_, this_.sign_subj as y7_, this_.sign_org as
           |                 |      | y8_, this_.author as y9_ from SOME_TABLE this_ left outer join SOME_TABLE2 authoruser1_ on this_.author=authoruser1_.id where ((this_.author
           |                 |      | is null or this_.author=:1  or authoruser1_.owner=:2  or this_.author in (select user_.id as y0_ from SOME_TABLE2 user_ where user_.region=:3 )) and
           |                 |      | this_.author is not null and this_.service in (:4 , :5 , :6 , :7 , :8 , :9 , :10 , :11 , :12 , :13 , :14 , :15 , :16 , :17 , :18 , :19 , :20 , :21 ,
           |                 |      | :22 , :23 , :24 , :25 , :26 , :27 , :28 , :29 , :30 , :31 , :32 , :33 , :34 , :35 , :36 , :37 , :38 , :39 , :40 , :41 , :42 , :43 , :44 , :45 , :46 ,
           |                 |      | :47 , :48 , :49 , :50 , :51 , :52 , :53 , :54 , :55 , :56 , :57 , :58 , :59 , :60 , :61 , :62 , :63 , :64 , :6



 CH# | SQL_ID        | PARENT_HANDLE    | OBJECT_HANDLE    |  PLAN_HASH |     PARSES |   H_PARSES | EXECUTIONS |    FETCHES | ROWS_PROCESSED | ROWS_PER_FETCH |    CPU_SEC | CPU_SEC_EXEC |    ELA_SEC |       LIOS |       PIOS |      SORTS | USERS_EXECUTING | B_Sens | B_Aware
---- | ------------- | ---------------- | ---------------- | ---------- | ---------- | ---------- | ---------- | ---------- | -------------- | -------------- | ---------- | ------------ | ---------- | ---------- | ---------- | ---------- | --------------- | ------ | -------
   2 | d3tcbyxaa65ku | 00000004A07EB2B8 | 0000000555482BF8 | 1496851868 |      18565 |          2 |      18566 |     541935 |        5415140 |     9.99223154 | 81859.0228 |   4.40908234 | 145650.218 | 3694696752 |  244581883 |          0 |               5 | N      | N

Elapsed: 00:00:00.14

ASH_SQLMON

18:44:29 (3)system@some_database> @ash_sqlmon d3tcbyxaa65ku 1496851868 %
old   8:    where sql_id = '&1'
new   8:    where sql_id = 'd3tcbyxaa65ku'
old   9:      and sql_plan_hash_value = nvl('&2', sql_plan_hash_value)
new   9:      and sql_plan_hash_value = nvl('1496851868', sql_plan_hash_value)
old  10:    -- and NVL(sql_exec_id, 0) = nvl('&3', NVL(sql_exec_id, 0))
new  10:    -- and NVL(sql_exec_id, 0) = nvl('%', NVL(sql_exec_id, 0))

        ID | PLAN_OPERATION                                                                   | OBJECT_OWNER         | OBJECT_NAME                    | WAIT_PROFILE
---------- | -------------------------------------------------------------------------------- | -------------------- | ------------------------------ | --------------------------------------------------------------------------------
         0 |   SELECT STATEMENT                                                               | <NULL>               | <NULL>                         | ON CPU(351); ON CPU(135);
         1 |     VIEW                                                                         | <NULL>               | <NULL>                         | ON CPU(97);
         2 |       COUNT STOPKEY                                                              | <NULL>               | <NULL>                         | ON CPU(2);
         3 |         VIEW                                                                     | <NULL>               | <NULL>                         | ON CPU(29901); direct path read(26326); buffer exterminate(1);
         4 |           FILTER                                                                 | <NULL>               | <NULL>                         | ON CPU(1464); latch: cache buffers chains(2);
         5 |             NESTED LOOPS OUTER                                                   | <NULL>               | <NULL>                         | ON CPU(63);
         6 |               TABLE ACCESS BY INDEX ROWID                                        | some_user            | SOME_TABLE                     | ON CPU(7201); db file sequential read(67); read by other session(54); gc buffer
           |                                                                                  |                      |                                | busy acquire(4);
         7 |                 INDEX FULL SCAN DESCENDING                                       | some_user            | SOME_TABLE_REDIF_IDX           | ON CPU(642); read by other session(6); db file sequential read(4); gc buffer bus
           |                                                                                  |                      |                                | y acquire(1);

         8 |               TABLE ACCESS BY INDEX ROWID                                        | some_user            | SOME_TABLE2                    | ON CPU(1403);
         9 |                 INDEX UNIQUE SCAN                                                | some_user            | SYS_C00288211                  | ON CPU(2507);
        10 |             TABLE ACCESS BY INDEX ROWID                                          | some_user            | SOME_TABLE2                    | ON CPU(473);
        11 |               INDEX UNIQUE SCAN                                                  | some_user            | SYS_C00288211                  | ON CPU(1239); latch: cache buffers chains(5);

look at plan line 3 in ash:


(3)system@some_database> @ash_obj d3tcbyxaa65ku  1496851868 sysdate-1/24 sysdate
old   4:   where a.sql_id='&1' and a.sql_plan_hash_value='&2' and a.SAMPLE_TIME between &3 and nvl(&4,sysdate)
new   4:   where a.sql_id='d3tcbyxaa65ku' and a.sql_plan_hash_value='1496851868' and a.SAMPLE_TIME between sysdate-1/24 and nvl(sysdate,sysdate)

  COUNT(*) | SQL_PLAN_LINE_ID | CURRENT_OBJ# | OBJECT_NAME                    | OWNER                          | SESSION | Event
---------- | ---------------- | ------------ | ------------------------------ | ------------------------------ | ------- | ----------------------------------------
      6366 |                3 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
      2446 |                3 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | WAITING | direct path read
      1511 |                6 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
       474 |                9 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
       298 |                8 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
       290 |                4 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
       212 |               11 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
       140 |                7 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
        95 |               10 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
        72 | <NULL>           |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
        25 |                0 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
        13 |                1 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
        11 |                5 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>
         2 |                4 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | WAITING | latch: cache buffers chains
         1 |                2 |       669478 | SYS_LOB0000669470C00005$$      | some_user                        | ON CPU  | <NULL>

 (3)system@some_database> l
  1  select count(*),a.SQL_PLAN_LINE_ID,current_obj#,o.object_name,o.owner,session_state,event
  2    from gv$active_session_history a
  3       left join dba_objects o on a.current_obj#=o.object_id
  4    where a.sql_id='&1' and a.sql_plan_hash_value='&2' and a.SAMPLE_TIME between &3 and nvl(&4,sysdate)
  5    group by a.SQL_PLAN_LINE_ID,a.current_obj#,o.object_name,o.owner,session_state,event
  6*   order by 1 desc

select * from ( select row_.*, rownum rownum_ from ( select this_.id as y0_, this_.status as y1_, this_.service as y2_, this_.request_date as y3_, this_.response_timestamp as y4_, 
substr(this_.response_content, 0, 5) responseContent,
 this_.labels as y6_, this_.sign_subj as y7_, this_.sign_org as y8_, this_.author as y9_ from adp_conversation_out this_ left outer join adp_user authoruser1_ on this_.author=authoruser1_.id where ((this_.author is null or this_.author=:1 or authoruser1_.owner=:2 or this_.author in (select user_.id as y0_ from adp_user user_ where user_.region=:3 )) and this_.author is not null and this_.service in (:4 , :5 , :6 , :7 , :8 , :9 , :10 , :11 , :12 , :13 , :14 , :15 , :16 , :17 , :18 , :19 , :20 , :21 , :22 , :23 , :24 , :25 , :26 , :27 , :28 , :29 , :30 , :31 , :32 , :33 , :34 , :35 , :36 , :37 , :38 , :39 , :40 , :41 , :42 , :43 , :44 , :45 , :46 , :47 , :48 , :49 , :50 , :51 , :52 , :53 , :54 , :55 , :56 , :57 , :58 , :59 , :60 , :61 , :62 , :63 , :64 , :65 , :66 , :67 , :68 , :69 , :70 , :71 , :72 , :73 , :74 , :75 , :76 , :77 , :78 , :79 , :80 , :81 , :82 , :83 , :84 , :85 , :86 , :87 , :88 , :89 , :90 , :91 , :92 , :93 , :94 , :95 , :96 , :97 , :98 , :99 , :100 , :101 , :102 , :103 , :104 , :105 , :106 , :107 , :108 , :109 , :110 , :111 , :112 , :113 , :114 , :115 , :116 , :117 , :118 , :119 , :120 , :121 , :122 , :123 , :124 , :125 , :126 , :127 , :128 , :129 , :130 , :131 , :132 , :133 , :134 , :135 , :136 , :137 , :138 , :139 , :140 , :141 , :142 , :143 , :144 , :145 , :146 , :147 , :148 , :149 , :150 , :151 , :152 , :153 , :154 , :155 , :156 , :157 , :158 , :159 , :160 , :161 , :162 , :163 , :164 , :165 , :166 , :167 , :168 , :169 , :170 , :171 , :172 , :173 , :174 , :175 , :176 , :177 , :178 , :179 , :180 , :181 , :182 , :183 , :184 , :185 , :186 , :187 , :188 , :189 , :190 , :191 , :192 , :193 , :194 , :195 , :196 )) and this_.pgu_conv_id is null and this_.last_updated>:197 order by y3_ desc ) row_ where rownum <= :198 ) where rownum_ > :19

this substr(this_.response_content, 0, 5) query high compressed clob field

after talking with the developers on the subject, why would they need these first 5 characters, they agreed to remove them from the query. After editing query the server load is 3 times lower

Primary Sidebar

Яндекс.Метрика