[Oracle-l] FW: PGA size discrepancy

PGA_AGGREGATE_TARGET is not a limit, it can be exceeded.
PGA_AGGREGATE_TARGET is a guideline which tells oracle

how much memory do you want to devote to oracle servers. Your limit is
ridiculously low so Oracle is probably ignoring it

completely and is using its own default, which is something like 10% of the
available memory (just guessing here). Of course,

available memory doesn't have to be physical memory, it is virtual memory,
thus the numbers you see. Of course, that too

is not very precise, as it shows "sum" for the system. I would look into
session statistics and sum PGA for the user sessions.

This way, Oracle thinks that you have just defined the number of holes on
PGA sanctioned courses.



--

Mladen Gogala

Ext. 121

_____

From: DBA Deepak
Sent: Friday, October 21, 2005 2:38 AM
To: oracle-l_at_freelists.org
Subject: PGA size discrepancy

Hi All,

I executed the following statements.

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production

SQL> select name,VALUE/(1024*1024) MB from v$sysstat
2 where name like '%pga%';

NAME MB
---------------------------------------------------------------- ----------
session pga memory 18184.7367
session pga memory max 19962.1279

SQL> sho parameter pga

NAME TYPE VALUE
------------------------------------ -----------
------------------------------
pga_aggregate_target big integer 24M

One query:
as we do not have this much amount of Physical memory. And the
pga_aggregate_target is 24M only.

What might be the issue?