Your sample query would only have needed
one active area.
Another thought: although the maximum you
are allowed is 150M, Oracle may decide that
there is no point in giving it to you because it
won't improve your performance significantly,
but it might benefit other people if some of the
memory is
select BELNR,count(*)
from sapr3.bsis
group by BELNR
order by BELNR
This was the SQL running at that time.
-Original Message-
Sent: Tuesday, December 30, 2003 5:44 PM
To: Multiple recipients of list ORACLE-L
It is possible for a single session to require more
than one sort or hash are
Thanks, I found it from the materials.
Tanel.
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Wednesday, December 31, 2003 8:19 AM
> Chapter 9, page 33 - Cat-Hash-strophes
> in the seminar notes. (The page number
> may have changed a little).
>
Chapter 9, page 33 - Cat-Hash-strophes
in the seminar notes. (The page number
may have changed a little).
If you have a plan like this, all the leading
tables have been hashed into memory at
the same time.
HASH JOIN
TABLE ACCESS (FULL) OF TABLE_4
HASH JOIN
TABLE ACCESS (FULL) OF T
I've alway understood that joining occurs always in two steps, first two
tables, then their result (row source) with next table and so on, so there's
no need for more than 2 hash tables for example?
Tanel.
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]
It is possible for a single session to require more
than one sort or hash area at a time. For example
a 4 table hash could require 3 in-memory hash
tables (and therefore use 3 x hash_area_size
in the days before pga_agg_target).
Possibly your session used 150MB, but had
multiple areas open at on
Your "global memory bound" statistic from v$pgastat says that max work area
size is 100M. Maybe this 5% rule doesn't apply with large
pga_aggregate_targets. The documentation claims that this value can be
adjusted during db workload, so you might want to try to run your operation
several times in a
no. it
used 800 MB of tempspace in the end.
(also
see the tempsize column output from the query of the v$sql_workarea_active
view)
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Tuesday, December 30, 2003
3:35 PMTo: Multiple recipients of list ORACL
ject: max 5% of pga_aggregate_target for a single serial session
Hi,
First of all, thank you to all answered my last question.
Now I have another question related to my last one.
In my system, pga_aggregate_target is set to 3GB and I
think a session would have approximately 150MB work area
before temp
Hi,
First of all, thank you to all answered my last question.
Now I have another question related to my last one.
In my system, pga_aggregate_target is set to 3GB and I
think a session would have approximately 150MB work area
before temp space is needed (5% of 3GB).
But I did a test, it only used
10 matches
Mail list logo
