Performance Tunning - Could anyone please help

Question

I have a procedure which uses two offensive queries.The currenttime its taking is approximately 2 min in DEV and in PROD 20 min.
Target is to reduce time to less than a minute in DEV and max 5 min in PROD.
PROBLEM1######################### I think nothing much can be done here.
Correct me in case I am wrong.
Insert into TEMP_A ===> Global Temporary table
(col1,
col2,
col3,
col4,
col5,
col6,
col7,
col8,
col9,
col10,
col11,
col12,
col13,
col14)
Select distinct
o.value1
,decode (staticvalue1, 1,o.value2,NULL) ==> Static values are populated from some other table
,decode (staticvalue2,2,o.value2,NULL)
,o.value4
,o.value5
,decode (staticvalue3,1,o.value3,NULL)
,decode (staticvalue4,1,o.value4,NULL)
,decode (staticvalue5,1,o.value5,NULL)
,decode (staticvalue6,1,o.value6,NULL)
,decode (staticvalue7,1,o.value7,NULL)
,e.value1
,e.value2
,e.value3
,e.value4
from table1 o ==> Big table having 100000(1L) records daily transacational table
table2 e==> Big table having 2L records daily transactional table
table3 oe ==> small table of 14000 records
table4 ji ==> Just 500 records
where ji.id= static value==> passed as input to procedure and 1 record is retried for that id
and ji.col1= oe.col1
and oe.TIMESTAMP >=ji.TIMESTAMP
and o.TIMESTAMP < ji.TIMESTAMP+1
and o.orderid =OE.orderid
and e.eventid = oe.eventid
and e.TIMESTAMP >=ji.TIMESTAMP
and e.TIMESTAMP < ji.TIMESTAMP+1
table1 o ==> Indexed with orderid, TIMESTAMP
table2 e ==> Indexed with eventid, TIMESTAMP
After these are fed, a very small manipulation to TEMP_A ==> Global temp table
Then major offensive insert is fired.
By now TEMP_A contains 1500 records.
PROBLEM2######################################################################
Insert into TABLE5
(a,b,c,d,e,f,g,h,i,j,k,l,m)
select
hardcode value1,
hardcode value2,
c.value1
c.value2
c.value3
c.value4
MAX(TRUNC(e.TIMESTAMP))
decode(staticvalue,0,MAX(e.TIMESTAMP)
,1,MIN(e.TIMESTAMP)
SUM(e.value5) as quantity,
SUM(e.value6 * e.val7)/SUM e.value6 as price
decode(staticvalue,0,SUM(e.value5*e.val7)/SUM (e.value6),
1,ROUND(SUM(e.value5*e.val7)/SUM (e.value6), 4),
2,TRUNC(SUM(e.value5*e.val7)/SUM (e.value6), 4)) as consider
SYSDATE
'APP_NAME'
FROM
table1 o ==> Big table having 100000(1L) records daily transacational table(same tables as above)
table2 e==> Big table having 2L records daily transactional table(same tables as above)
table3 oe ==> small table of 14000 records(same tables as above)
table4 ji ==> Just 500 records (same tables as above)
TEMP_A c ( which is the same TEMP table populated earlier)
WHERE
ji.id= static value==> passed as input to procedure and 1 record is retried for that id
and ji.col1= oe.col1
and oe.TIMESTAMP >=ji.TIMESTAMP
and o.TIMESTAMP < ji.TIMESTAMP+1
and o.orderid =OE.orderid
and e.eventid = oe.eventid
and e.TIMESTAMP >=ji.TIMESTAMP
and e.TIMESTAMP < ji.TIMESTAMP+1
GROUP BY
c.value1
c.value2
c.value3
c.value4
The temp_A table is not indexed and its written as CREATE Global temporary ***** on commit preserve rows.
The SQL trace of the second problem as follows.
| Id | Operation | Name | Rows |
Bytes | Cost (%CPU)| Time | Pstart| Pstop |
| 0 | SELECT STATEMENT | | 1 |
428 | 30 (7)| 00:00:01 | | |
| 1 | SORT GROUP BY | | 1 |
428 | 30 (7)| 00:00:01 | | |
|* 2 | TABLE ACCESS BY LOCAL INDEX ROWID| table1 | 1 |
18 | 15 (0)| 00:00:01 | | |
| 3 | NESTED LOOPS | | 1 |
428 | 29 (4)| 00:00:01 | | |
|* 4 | HASH JOIN | | 1 |
410 | 14 (8)| 00:00:01 | | |
| 5 | NESTED LOOPS | | 4 |
860 | 8 (0)| 00:00:01 | | |
| 6 | TABLE ACCESS BY INDEX ROWID | table3 | 1 |
16 | 2 (0)| 00:00:01 | | |
|* 7 | INDEX UNIQUE SCAN | PK_table3 | 1 |
| 1 (0)| 00:00:01 | | |
|* 8 | TABLE ACCESS FULL | Table4 | 4 |
796 | 6 (0)| 00:00:01 | | |
| 9 | TABLE ACCESS FULL | TEMP_A | 1648 |
313K| 5 (0)| 00:00:01 | | |
| 10 | PARTITION RANGE ALL | | 1 |
| 14 (0)| 00:00:01 | 1 | 14 |
|* 11 | INDEX RANGE SCAN | PK_table2 | 1 |
| 14 (0)| 00:00:01 |
If other than global temporary table, problem can be resolved, also suggest for the same.

Answer 1

hi ,
perhaps you might want to try the insert into /*+ APPEND */ table_name or using SQL Loader (but i have not used it before though)
What i know of the APPEND hints is it reduces the logging but it should be recommend for inserting records of huge size as it moves pointer above the High-Water-Mark (i.e i think that some spaces will be wasted for those below the HWM)
hope that might help
tks & rgds