Analysis of a trace - tkprof

Question

Hello, I would like to locate the root of a very slow execution of a package at the base. For this to make a trace session on the last run it took 77 minutes to complete.
Then he saw the information on after turning it with tkprof. In the first part are the most expensive operations, and ultimately the overall results.
Database Version: 10.2.0.4.0
Standard Edition - RAC - ASM
total RAM        16G
sga_target      1504M
db_cache_size 0
owner            XAJTDB
--Package/procedure executed (from a job)
BEGIN HISR_FUTURE.p_hisr_future_all; END;--file  xa212_j000_14811348.trc
TKPROF: Release 10.2.0.4.0 - Production on Fri Feb 1 15:23:26 2013
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
Trace file: xa212_j000_14811348.trc
Sort options: fchela 
*SELECT MAX(UTCTIME)*
*FROM*
*CONECT_01 WHERE POINTNUMBER=:device_1*
call             count       cpu        elapsed       disk      query     current    rows
Parse         1776        0.05       0.03           0                0           0            0
Execute     1776        0.04       0.11           0               0            0            0
Fetch         3553       51.58     2256.05      405620  552615     0           1776
total       7105        51.67     2256.21      405620  552615     0           1776
Misses in library cache during parse: 0
Misses in library cache during execute: 1
Parsing user id: 57  (XAJTDB)   (recursive depth: 2)
Rows     Execution Plan
      0  SELECT STATEMENT   MODE: ALL_ROWS
      0   SORT (AGGREGATE)
      0    FIRST ROW
      0     INDEX   MODE: ANALYZED (FULL SCAN (MIN/MAX)) OF
                'CONECT_01_PK' (INDEX (UNIQUE))
*SELECT MAX(UTCTIME)*
*FROM*
*STATUS_01 WHERE POINTNUMBER=:device_1*
call          count       cpu    elapsed       disk      query    current     rows
Parse       8206      0.20       0.15          0          0          0           0
Execute   8206      0.25       0.55          0          0          0           0
Fetch     16412     23.09      38.80       39     869129      0        8206
total      32824     23.54      39.50        39     869129      0        8206
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: 57  (XAJTDB)   (recursive depth: 2)
Rows     Row Source Operation
      1  SORT AGGREGATE (cr=35 pr=33 pw=0 time=209038 us)
      1   FIRST ROW  (cr=35 pr=33 pw=0 time=209020 us)
      1    INDEX FULL SCAN (MIN/MAX) STATUS_01_PK (cr=35 pr=33 pw=0 time=209019 us)(object id 79195)
Rows     Execution Plan
      0  SELECT STATEMENT   MODE: ALL_ROWS
      1   SORT (AGGREGATE)
      1    FIRST ROW
      1     INDEX   MODE: ANALYZED (FULL SCAN (MIN/MAX)) OF
                'STATUS_01_PK' (INDEX (UNIQUE))
*OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS*
call     count       cpu    elapsed       disk      query    current     rows
Parse        0      0.00       0.00          0          0          0           0
Execute    0      0.00       0.00          0          0          0           0
Fetch       0      0.00       0.00          0          0          0           0
total        0      0.00       0.00          0          0          0           0
Misses in library cache during parse: 0
*OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS*
call          count        cpu      elapsed           disk         query      current        rows
Parse       97568       4.17         4.94              0             38              2           0
Execute 111405    146.92    2382.98     465031    1337316    1715361       85314
Fetch      46033     75.20     2297.66     406057    1461528               0       36908
total      255006    226.29    4685.59     871088    2798882    1715363      122222
Misses in library cache during parse: 8451
Misses in library cache during execute: 153
94798  user  SQL statements in session.
4557  internal SQL statements in session.
99355  SQL statements in session.
   48  statements EXPLAINed in this session.
Trace file: xa212_j000_14811348.trc
Trace file compatibility: 10.01.00
Sort options: fchela 
       1  session in tracefile.
   94798  user  SQL statements in trace file.
    4557  internal SQL statements in trace file.
   99355  SQL statements in trace file.
    8398  unique SQL statements in trace file.
      48  SQL statements EXPLAINed using schema:
           XAJTDB.prof$plan_table
             Default table was used.
             Table was created.
             Table was dropped.
  707680  lines in trace file.
    2502  elapsed seconds in trace file.I think the memory settings are correct.
May bring me ideas on these overall results indicate?
The tables involved have a large volume of data (to 15 million, as appropriate). They are not partitioned (remember is Standard Edition) , is this one of the reasons why the job run so slow?.
Please require me more information if necessary.
Thanks!
Edited by: user12086565 on 26/03/2013 07:38
Edited by: user12086565 on 26/03/2013 09:31

Answer 1

Hi, here the output of the information request:
PROMPT ALTER TABLE xajtdb.status_01 ADD CONSTRAINT status_01_pk PRIMARY KEY
ALTER TABLE xajtdb.status_01
  ADD CONSTRAINT status_01_pk PRIMARY KEY (
    utctime,
    pointnumber
  USING INDEX
    TABLESPACE xa_hisr_hist_data_ts
    PCTFREE   10
    INITRANS   2
    MAXTRANS 255
    STORAGE (
      INITIAL 1310720 K
      NEXT          0 K
      MINEXTENTS    1
      MAXEXTENTS    UNLIMITED
      PCTINCREASE   0
      FREELISTS     1
      FREELIST GROUPS 1
      BUFFER_POOL DEFAULT
    LOGGING
    NOCOMPRESS
PROMPT ALTER TABLE xajtdb.conect_01 ADD CONSTRAINT conect_01_pk PRIMARY KEY
ALTER TABLE xajtdb.conect_01
  ADD CONSTRAINT conect_01_pk PRIMARY KEY (
    utctime,
    pointnumber
  USING INDEX
    TABLESPACE xa_hisr_hist_data_ts
    PCTFREE   10
    INITRANS   2
    MAXTRANS 255
    STORAGE (
      INITIAL  647168 K
      NEXT          0 K
      MINEXTENTS    1
      MAXEXTENTS    UNLIMITED
      PCTINCREASE   0
      FREELISTS     1
      FREELIST GROUPS 1
      BUFFER_POOL DEFAULT
    LOGGING
    NOCOMPRESS
select
table_name,num_rows,
blocks,avg_space,
chain_cnt,avg_row_len,
sample_Size
from dba_tables
where table_name = 'CONECT_01';
TABLE_NAME NUM_ROWS BLOCKS AVG_SPACE CHAIN_CNT AVG_ROW_LEN SAMPLE_SIZE
CONECT_01  16195993  92861      1738         0          24        5484
===============================================================================
select
table_name,num_rows,
blocks,avg_space,
chain_cnt,avg_row_len,
sample_Size
from dba_tables
where table_name = 'STATUS_01';
TABLE_NAME NUM_ROWS BLOCKS AVG_SPACE CHAIN_CNT AVG_ROW_LEN SAMPLE_SIZE
STATUS_01  46835851 262443       948         0          23        5563
===============================================================================
select
index_name,num_rows,
leaf_blocks,sample_Size
from dba_indexes
where table_name = 'CONECT_01';
INDEX_NAME        NUM_ROWS LEAF_BLOCKS SAMPLE_SIZE
CONECT_01_PK      15883091       84054      199734
CONECT_01_I_POINT 16110657       85489      217286
===============================================================================
select
index_name,num_rows,
leaf_blocks,sample_Size
from dba_indexes
where table_name = 'STATUS_01';
INDEX_NAME        NUM_ROWS LEAF_BLOCKS SAMPLE_SIZE
I_STATUS_01_POINT 45950607      235104      210693
STATUS_01_PK      46651458      242459      204916
===============================================================================
select OWNER,TABLE_NAME,NUM_DISTINCT,LAST_ANALYZED
from ALL_TAB_COLUMNS
where TABLE_NAME = 'CONECT_01’;
OWNER  TABLE_NAME NUM_DISTINCT LAST_ANALYZED
XAJTDB CONECT_01          5646 01/04/2013 22:19:12
XAJTDB CONECT_01          2777 01/04/2013 22:19:12
XAJTDB CONECT_01           695 01/04/2013 22:19:12
XAJTDB CONECT_01             5 01/04/2013 22:19:12
===============================================================================
select OWNER,TABLE_NAME,NUM_DISTINCT,LAST_ANALYZED
from ALL_TAB_COLUMNS
where TABLE_NAME = 'STATUS_01';
OWNER  TABLE_NAME NUM_DISTINCT LAST_ANALYZED
XAJTDB STATUS_01          5626 01/04/2013 22:21:17
XAJTDB STATUS_01          8342 01/04/2013 22:21:17
XAJTDB STATUS_01            27 01/04/2013 22:21:17
XAJTDB STATUS_01             2 01/04/2013 22:21:17
===============================================================================Thanks!