Low performance (please help)

Question

Hi!
My DB objects are:create or replace TYPE T_G5RPP AS VARRAY(1000) OF NUMBER(2);
CREATE TABLE "ROGADM"."ROG_TEMP_G5LKL" (
    "ID"     VARCHAR2(100 BYTE),
    "STATUS" NUMBER(2,0) DEFAULT 1,
    "G5IDL"  VARCHAR2(200 BYTE),
    "G5TLOK" NUMBER(1,0),
    "G5PEW"  NUMBER,
    "G5PPP"  NUMBER,
    "G5LIZ"  NUMBER(32,0),
    "G5LPP"  NUMBER(6,0),
    "G5RPP"  "ROGADM"."T_G5RPP",
    "G5WRT"  NUMBER(32,0),
    "G5DWR"  DATE,
    "G5DTW"  DATE,
    "G5DTU"  DATE,
    "ID_G5ADR_RADR" VARCHAR2(100 BYTE),
    "ID_G5JDR_RJDR" VARCHAR2(100 BYTE),
    "ID_G5BUD_RBUD" VARCHAR2(100 BYTE),
    "IDR"           VARCHAR2(100 BYTE),
    "PLS_ID"        NUMBER
CREATE INDEX "T_G5LKL_ADR_FK" ON "ROG_TEMP_G5LKL" (PLS_ID, "ID_G5ADR_RADR");
CREATE INDEX "T_G5LKL_BUD_FK" ON "ROG_TEMP_G5LKL" (PLS_ID, "ID_G5BUD_RBUD");
CREATE INDEX "T_G5LKL_JDR_FK" ON "ROG_TEMP_G5LKL" (PLS_ID, "ID_G5JDR_RJDR");
create unique index T_G5LKL_PK on ROG_TEMP_G5LKL(PLS_ID, ID);
function get_obr_ark_dzi(p_obk_typ varchar2, p_obk_id varchar2, p_co varchar2, p_pls_id number)
  return varchar2 deterministic
AS
  v_obk_typ varchar2(10);
  v_obk_id  G5ADR.ID%type;
  v_out   varchar2(400);
  v_sep   varchar2(2) := '';
  v_old   varchar2(10) := '';
  v_pls_id    number;
begin
  if p_obk_typ not in ('G5DZE','G5BUD','G5LKL','G5OBR','G5KLU','G5UDZ','G5UDW','G5JDR', 'G5ADR') then
    return null;
  end if;
  v_obk_typ := p_obk_typ;
  v_obk_id  := p_obk_id;
  v_pls_id  := p_pls_id;
  if v_obk_typ = 'G5ADR' then
    -- sprawdzenie, adresem czego jest ten adres
    -- (odczytane będą dane dla adresów działek, budynków lub lokali, które są podpięte do tylko 1 obiektu)
    declare
      v_id  G5LKL.ID%type;
      v_co  varchar2(3);  -- ...jest adresem tego
    begin
      /** START **/
      begin
        v_co := 'LKL';
        execute immediate 'SELECT ID FROM ROG_TEMP_G5LKL WHERE ID_G5ADR_RADR = :obk AND pls_id = :pls'
           into v_id
          using v_obk_id, v_pls_id;
      exception when no_data_found then
        v_co := null;
      end;
      /** END **/
      if v_co is not null then
        v_obk_typ := 'G5'||v_co;
        v_obk_id  := v_id;
      else
        return null;
      end if;
    end;
  end if;
  if v_obk_typ = 'G5LKL' then
    execute immediate
'   SELECT case when :p_co=''obreb'' then    SUBSTR(G5IDL,10,4)
                when :p_co=''arkusz'' then   SUBSTR(G5IDL,18,INSTR(G5IDL,''.'',-1,3)-18)
                when :p_co=''dzialka'' then  SUBSTR(G5IDL,
         instr(G5IDL,''.'',1,2 + case when SUBSTR(G5IDL,15, 3)=''AR_'' then 1 else 0 end) + 1,
         instr(G5IDL,''.'',-1,2)-1 - instr(G5IDL,''.'',1,2 + case when SUBSTR(G5IDL,15, 3)=''AR_'' then 1 else 0 end))
           end
      FROM ROG_TEMP_G5LKL
     WHERE ID = :p_obk_id AND pls_id = :pls' into v_out using p_co,p_co,p_co, v_obk_id, v_pls_id;
  else
    return null;
  end if;
  return v_out;
exception
  when no_data_found then
    return null;
end get_obr_ark_dzi;I have a query:SELECT log_pls_id,log_obk_id,
       log_obk_typ
       ,rog_pck_utl.get_obr_ark_dzi(log_obk_typ, log_obk_id, 'obreb', log_pls_id) AS log_obk_obreb
  FROM (SELECT distinct log_obk_id, log_obk_typ, log_pls_id
          FROM rog_log_ksat_zdarzenia
          JOIN rog_log on logkz_log_id = log_id
         WHERE logkz_f_obsluzony <> 'T')
   where log_obk_typ = 'G5ADR' and log_pls_id = 635 and rownum <= 200; which runs 7.2 seconds. When I comment the block bounded by /** START **/ and /** END **/ the query runs only 0.043 seconds.
Here is part of trace file:SELECT log_pls_id,log_obk_id,
       log_obk_typ
       ,rog_pck_utl.get_obr_ark_dzi(log_obk_typ, log_obk_id, 'obreb', log_pls_id) AS log_obk_obreb
  FROM (SELECT distinct log_obk_id, log_obk_typ, log_pls_id
          FROM rog_log_ksat_zdarzenia
          JOIN rog_log on logkz_log_id = log_id
         WHERE logkz_f_obsluzony <> 'T')
   where log_obk_typ = 'G5ADR' and log_pls_id = 635 and rownum <= 200
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      0.06       0.10          0       2480          0         200
total        3      0.06       0.11          0       2480          0         200
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 379  (ROGADM)
Rows     Execution Plan
      0  SELECT STATEMENT   MODE: ALL_ROWS
      0   COUNT (STOPKEY)
      0    VIEW
      0     SORT (UNIQUE NOSORT)
      0      TABLE ACCESS   MODE: ANALYZED (BY INDEX ROWID) OF
                 'ROG_LOG_KSAT_ZDARZENIA' (TABLE)
      0       NESTED LOOPS
      0        TABLE ACCESS   MODE: ANALYZED (BY INDEX ROWID) OF
                   'ROG_LOG' (TABLE)
      0         INDEX   MODE: ANALYZED (RANGE SCAN) OF 'LOG_I'
                    (INDEX (UNIQUE))
      0        INDEX   MODE: ANALYZED (RANGE SCAN) OF
                   'LOGKZ_LOG_FK_I' (INDEX)
SELECT ID
FROM
ROG_TEMP_G5LKL WHERE ID_G5ADR_RADR = :obk AND pls_id = :pls
call     count       cpu    elapsed       disk      query    current        rows
Parse       42      0.00       0.00          0          0          0           0
Execute     98      0.00       0.00          0          0          0           0
Fetch       98      7.82       7.58          0    4519564          0           0
total      238      7.82       7.58          0    4519564          0           0
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 379  (ROGADM)   (recursive depth: 1)
Rows     Row Source Operation
      0  TABLE ACCESS BY INDEX ROWID ROG_TEMP_G5LKL (cr=138354 pr=0 pw=0 time=231295 us)
205593   INDEX RANGE SCAN T_G5LKL_PK (cr=576 pr=0 pw=0 time=411229 us)(object id 433034)
Rows     Execution Plan
      0  SELECT STATEMENT   MODE: ALL_ROWS
      0   TABLE ACCESS   MODE: ANALYZED (BY INDEX ROWID) OF
              'ROG_TEMP_G5LKL' (TABLE)
205593    INDEX   MODE: ANALYZED (RANGE SCAN) OF 'T_G5LKL_ADR_FK' (INDEX)
(...)What do you think is the reason of such big value in 'query' column of 'Fetch'?
Explain plan executed from SQL Developer is different:explain plan for
SELECT ID
  FROM ROG_TEMP_G5LKL
WHERE ID_G5ADR_RADR = :adr
   AND pls_id = 630;
PLAN_TABLE_OUTPUT
Plan hash value: 3052821629
| Id  | Operation                   | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT            |                |     1 |   117 |     3   (0)| 00:00:01 |
|*  1 |  TABLE ACCESS BY INDEX ROWID| ROG_TEMP_G5LKL |     1 |   117 |     3   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | T_G5LKL_PK     |     1 |       |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(ID_G5ADR_RADR=:ADR)
   2 - access(PLS_ID=630)Please help...

Answer 1

Yes, this index can be unique:SELECT count(*)
  FROM ROG_TEMP_G5LKL
GROUP BY pls_id, ID_G5ADR_RADR
HAVING count(*) > 1;
no rows selectedUnfortunately statistics are not up to date. I can't gather it, because DBA must fix some DB blocks first.
Edited by: JackK on Aug 5, 2011 7:20 AM
I've found something! When I add a condition to WHERE clause:SELECT log_pls_id,log_obk_id,
       log_obk_typ
       ,rog_pck_utl.get_obr_ark_dzi(log_obk_typ, log_obk_id, 'obreb', log_pls_id) AS log_obk_obreb
       ,rog_pck_utl.get_obr_ark_dzi(log_obk_typ, log_obk_id, 'arkusz', log_pls_id) AS log_obk_AR
       ,rog_pck_utl.get_obr_ark_dzi(log_obk_typ, log_obk_id, 'dzialka', log_pls_id) AS log_obk_dze
  FROM (SELECT distinct log_obk_id, log_obk_typ, log_pls_id
          FROM rog_log_ksat_zdarzenia
          JOIN rog_log on logkz_log_id = log_id
         WHERE logkz_f_obsluzony <> 'T')
   where log_obk_typ = 'G5ADR' and log_pls_id = 635 and rownum <= 200
     and exists (select 1 from g5lkl where id_g5adr_radr = log_obk_id);   -- added conditionthe statement runs in about 1 second. Without the condition it takes 22.4 seconds to complete. I think that's because in the latter case the querySELECT ID FROM G5LKL ... did not find any row.
Edited by: JackK on Aug 8, 2011 6:16 AM
I changed the index T_G5LKL_ADR_FK to:CREATE INDEX T_G5LKL_ADR_FK_ID ON ROG_TEMP_G5LKL (PLS_ID, ID_G5ADR_RADR, ID);and it runs fast enought - *200 rows in 1-2 seconds*. Now the plan shows only INDEX RANGE SCAN.