Temporary table space usage

Question

Hi could someone help me ...
for the following query...
SELECT returnflag
, linestatus
, sum(quantity) as sum_qty
, sum(extendedprice) as sum_base_price
, sum(extendedprice * (1 - iscount)) as sum_disc_price
, sum(extendedprice * (1 - iscount) * (1 + l_tax)) as sum_charge
, avg(quantity) as avg_qty, avg(extendedprice) as avg_price
, avg(iscount) as avg_disc, count(*) as count_order
FROM lineitem
WHERE shipdate <= date '1998-12-01'
GROUP BY returnflag, linestatus
ORDER BY returnflag, linestatus;
Explain Plan :
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 5 | 135 | 299K (2)| 01:00:00 |
| 1 | SORT GROUP BY | | 5 | 135 | 299K (2)| 01:00:00 |
|* 2 | TABLE ACCESS FULL| LINEITEM | 57M| 1493M| 297K (1)| 00:59:35 |
Predicate Information (identified by operation id):
2 - filter("L_SHIPDATE"<=TO_DATE(' 1998-09-02 00:00:00',
'syyyy-mm-dd hh24:mi:ss'))
would any parts of this query be carried out on the temporary table space (sums and averages? / sort group by?) ... or what impact would the temp table space have when running this query?
any help would be appriciated

Answer 1

im using 11g r2,
what about usage of temporary table space (approximatly) with the following ..
============================================
create view revenue (supplier_no, total_revenue) as
select
suppkey, sum(extendedprice * (1 - iscount))
from
lineitem
where
shipdate >= date '1994-12-01'
group by
suppkey;
select suppkey, name, address, phone, total_revenue
from supplier, revenue
where suppkey = supplier_no and total_revenue = (select max(total_revenue)from revenue)
order by suppkey;
==========================================================
View created.
Execution Plan
Plan hash value: 2790460729
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)|
Time |
| 0 | SELECT STATEMENT | | 50000 | 5126K| | 381K (1)|
01:16:23 |
| 1 | MERGE JOIN | | 50000 | 5126K| | 381K (1)|
01:16:23 |
| 2 | SORT JOIN | | 100K| 3027K| | 380K (1)|
01:16:09 |
|* 3 | VIEW | REVENUE | 100K| 3027K| | 380K (1)|
01:16:09 |
| 4 | WINDOW BUFFER | | 100K| 2148K| | 380K (1)|
01:16:09 |
| 5 | HASH GROUP BY | | 100K| 2148K| 1207M| 380K (1)|
01:16:09 |
|* 6 | TABLE ACCESS FULL| LINEITEM | 34M| 733M| | 297K (1)|
00:59:35 |
|* 7 | SORT JOIN | | 50000 | 3613K| 8712K| 1182 (1)|
00:00:15 |
| 8 | TABLE ACCESS FULL | SUPPLIER | 50000 | 3613K| | 308 (1)|
00:00:04 |
Predicate Information (identified by operation id):
3 - filter("TOTAL_REVENUE"="ITEM_1")
6 - filter("L_SHIPDATE">=TO_DATE(' 1994-12-01 00:00:00', 'syyyy-mm-dd
hh24:mi:ss'))
7 - access("S_SUPPKEY"="SUPPLIER_NO")
filter("S_SUPPKEY"="SUPPLIER_NO")
Statistics
=========================================================
presumably temp table space will be used for sort and merge joins? .. but how does temp table space work with the view?