Академический Документы
Профессиональный Документы
Культура Документы
The PGA is a memory region containing data and control information for a single
process (server or background). One PGA is allocated for each server process; the
PGA is exclusive to that server process and is read and written only by Oracle code
acting on behalf of that process. A PGA is allocated by Oracle when a user connects
to an Oracle database and a session is created.
In order to determine the proper size of PGA, we need to examine the measuring
criteria from performance views.
Oracle official document about v$pgastat has good explanation for every field
within that view.
NAME VALUE
-------------------------------------------------- ----------
aggregate PGA target parameter 550502400
aggregate PGA auto target 34406400
total PGA inuse 1200735232
total PGA allocated 1520827392
over allocation count 573252
extra bytes read/written 1.2234E+10
cache hit percentage 99.83
OraclePoint.com
7 rows selected.
We noticed that “total PGA inuse”is around 1.2G, which is far larger
than “aggregate PGA target”(550M). Similarly, “ total PGA allocated”is
almost 3 times of “ aggregate PGA target” . “over allocation count”
happen if the value of PGA_AGGREGATE_TARGET is too small and it in
turn causes lots of system I/O, as indicated as “
extra bytes
read/written”.
OraclePoint.com
We have 41 ONEPASS upon output. That’ s not bad because we have 0
MULTIPASS. But, the ideal case is that all are OPTIMAL. Therefore, we
need to do proper adjustment on PGA size.
OraclePoint.com
15 rows selected.
NAME VALUE
-------------------------------------------------- ----------
workarea executions - onepass 3
workarea executions - multipass 0
workarea executions - optimal 702865
NAME VALUE
-------------------------------------------------- ----------
workarea executions - onepass 948
workarea executions - multipass 6
workarea executions - optimal 81119656
The joining query above also shows that the PGA size is not set
properly because the number of ONEPASS and MULTIPASS are
considerable.
OraclePoint.com
Based on above findings, we should increase the PGA size through query
view V$PGA_TARGET_ADVICE.
14 rows selected.
OraclePoint.com