Aertlog:Thu Jun 25 16:27:07 2015
WARNING: Granules of pga_aggregate_target 200 cannot be more than memory_target (201) - sga_target (0) or min_sga (5)
Thu Jun 25 16:33:11 2015
WARNING: Granules of pga_aggregate_target 200 cannot be more than memory_target (201) - sga_target (0) or min_sga (5)
Thu Jun 25 16:54:42 2015
WARNING: Granules of pga_aggregate_target 200 cannot be more than memory_target (201) - sga_target (0) or min_sga (5)
Thu Jun 25 17:00:45 2015
WARNING: Granules of pga_aggregate_target 200 cannot be more than memory_target (201) - sga_target (0) or min_sga (5)
SQL> show parameter sga
NAME
TYPE
VALUE
------------------------------------ ----------- ------------------------------
lock_sga
boolean
FALSE
pre_page_sga
boolean
FALSE
sga_max_size
big integer 102912M
sga_target
big integer 0
SQL> show parameter mem
NAME
TYPE
VALUE
------------------------------------ ----------- ------------------------------
hi_shared_memory_address
integer
0
memory_max_target
big integer 102912M
memory_target
big integer 102912M
shared_memory_address
integer
0
SQL> show parameter pga
NAME
TYPE
VALUE
------------------------------------ ----------- ------------------------------
pga_aggregate_target
big integer 0
SQL>
参考:
WARNING: GRANULES OF PGA_AGGREGATE_TARGET CANNOT BE MORE THAN MEMORY_TARGET (文档 ID 970274.1) 转到底部转到底部
In this Document
Symptoms
Changes
Cause
Solution
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.1.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Aug-2014***
SYMPTOMS
The following message is reported in the alert log:
WARNING: Granules of pga_aggregate_target %d cannot be more than memory_target (%d) - sga_target (%d) or min_sga(%d)
CHANGES
The MEMORY_TARGET and SGA_MAX_SIZE or SGA_TARGET parameters are set.
CAUSE
This warning message is raised because the MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_MAX_SIZE/SGA_TARGET parameters are set the same.
However, in Oracle 11g the MEMORY_TARGET parameter defines the total amount of memory that Oracle can use, which incorporates both SGA and PGA areas.
Therefore if these are set the same as the SGA_MAX_SIZE/SGA_TARGET parameters then this leaves no memory available for the PGA, and hence this warning message is raised.
SOLUTION
Ensure that the MEMORY_TARGET/MEMORY_MAX_TARGET parameter settings are set to at least the sum of SGA_MAX_SIZE/SGA_TARGET plus the PGA_AGGREGATE_TARGET parameter.