Which of these are good starting points to use when configuring the maximum values for SGA and PGA, based on the amount of memory available on the system?

The DBA has chosen to manage SGA and PGA memory separately in an OLTP database
because of his unique knowledge of the application.
Which of these are good starting points to use when configuring the maximum values for
SGA and PGA, based on the amount of memory available on the system?

The DBA has chosen to manage SGA and PGA memory separately in an OLTP database
because of his unique knowledge of the application.
Which of these are good starting points to use when configuring the maximum values for
SGA and PGA, based on the amount of memory available on the system?

A.
20% SGA, 80% PGA

B.
25% SGA, 75% PGA

C.
50% SGA, 50% PGA

D.
75% SGA, 25% PGA

E.
80% SGA, 20% PGA

Show Hint

Leave a Reply 1

Your email address will not be published. Required fields are marked *

Jake from SF

Jake from SF

E is correct: 20% memory given to PGA when WORKAREA_SIZE_POLICY is set to AUTO.

https://docs.oracle.com/cd/B28359_01/server.111/b28320/initparams177.htm

Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO. This means that SQL working areas used by memory-intensive SQL operators (such as sort, group-by, hash-join, bitmap merge, and bitmap create) will be automatically sized. A nonzero value for this parameter is the default since, unless you specify otherwise, Oracle sets it to 20% of the SGA or 10 MB, whichever is greater.

Reply