This discussion is archived
10 Replies Latest reply: Nov 3, 2012 7:53 AM by JohnWatson RSS

WARNING: Granules of pga_aggregate_target 380 cannot be more than memory_ta

user569151 Newbie
Currently Being Moderated
I got above warning in the production 11.2.0.3 environment.

When I create the db using dbca, I choose memory target of certain number and clicked automatic memory management.
here is the target information in show parameter:

SQL> show parameter target

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
archive_lag_target integer 0
db_flashback_retention_target integer 7200
fast_start_io_target integer 0
fast_start_mttr_target integer 300
memory_max_target big integer 47744M
memory_target big integer 47744M
parallel_servers_target integer 256
pga_aggregate_target big integer 0
sga_target big integer 0

However if I create a pfile from spfile, there are a whole bunch of paramter target set in each instance:
PRD1.__db_cache_size=20401094656
PRD2.__db_cache_size=17985175552
PRD1.__java_pool_size=134217728
PRD2.__java_pool_size=134217728
PRD1.__large_pool_size=268435456
PRD2.__large_pool_size=268435456
PRD1.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
PRD1.__pga_aggregate_target=48586817536
PRD2.__pga_aggregate_target=47781511168
PRD1.__sga_target=27783069696
PRD2.__sga_target=25501368320
PRD1.__shared_io_pool_size=0
PRD2.__shared_io_pool_size=0
PRD1.__shared_pool_size=4026531840
PRD2.__shared_pool_size=3892314112
PRD1.__streams_pool_size=0
PRD2.__streams_pool_size=0

How do I get around with this issue? I find there is an oracle note on this issue, however requires to bounce the db. since this is prod environment, we are not afford to bounce the db.

Any advice on this issue?

Thanks in advance.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points