Database Memory & 4030/4031 (MOSC)

MOSC Banner

ADDM recommends to resize undersized SGA and PGA even if database parameters have enough value?

edited Nov 9, 2019 9:50AM in Database Memory & 4030/4031 (MOSC) 7 commentsAnswered

SQL> show parameter MEMORY_MAX_TARGET

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

memory_max_target                    big integer 16G

SQL> show parameter MEMORY_TARGET

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

memory_target                        big integer 0

SQL> show parameter SGA_MAX_SIZE

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

sga_max_size                         big integer 14G

SQL> show parameter SGA_TARGET

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

sga_target                           big integer 14G

SQL> show parameter PGA_AGGREGATE_TARGET

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

pga_aggregate_target                 big integer 1079M

SQL> show parameter workarea_size_policy

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

workarea_size_policy                 string      AUTO

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center