Large pool or shared_pool_reserved_size

We recently got ORA-04031 few times. The help suggests to increase largepool of shared_pool_reserved_size. Some forums I read suggest that large_pool to be used only when using MTS. So, should we just use shared_pool_reserved_size and shared_pool_size settings for fixing the problem for non MTS parameters. Also is the default value for shared_pool_reserved_min_alloc sufficient ?

I've gotten ORA-04031 a couple times over the last few years. When it's happened I just increased the init.ora
parameter shared_pool_size and that fixed the problem. We're not using MTS. I think if you monitor your free
memory during peak usage from time to time you can tell when you might need to increase the shared_pool_size
to avoid ORA-04031.

Similar Messages

ORA-4031 [512024] [large pool] [unknown object] [large pool] [PX msg pool]

Hello Friends,
I am frequently getting error in alert.log file.
ORA-4031 [512024] [large pool] [unknown object] [large pool] [PX msg pool]
Database version: 11gR2
OS : Solaris 10
SGA Size 4gb
SGA Target 4112mb
I am unable to identify the cause for above error.
Some time database become hang.
I can also see many wait events "latch: parallel query alloc buffer"
Please guide me what could be the cause of this problem

Hi
Please check below which could be helpful for your issue:
Master Note for Diagnosing ORA-4031 [ID 1088239.1]
https://support.oracle.com/CSP/ui/flash.html#tab=Dashboard%28page=GRHome&id=gkzpuq90%28domainId=ORA4031%29%29
Regard
Helios

LARGE POOL의 개념 및 사용 방법

제품 : ORACLE SERVER
작성날짜 : 2004-05-03
LARGE POOL의 개념 및 사용 방법
1. 개념 및 사용 목적
Oracle8.0에서 large pool이라는 새로운 SGA 내의 구성이 도입되었다. large pool
이란 shared pool과 유사하나 실제 shared pool 내의 일부분을 사용하는 것은
아니고 SGA 내에 직접 할당하며, 이 pool을 사용할 수 있는 작업들을 제한하고 있다.
Oracle8에서 large pool을 사용하는 주요 목적은 다음과 같이 두가지로 볼 수 있다.
- MTS connection에서 session 정보, 즉 UGA를 할당하기 위해서
- sequential file IO의 buffering을 위해서
(예를 들어, multiple I/O slave를 사용하는 경우의 recovery)
MTS connection이 large pool을 사용하는 경우, 일단 fixed UGA라고 하는 부분은
shared large pool을 사용하고, 나머지 session memory(UGA)는 large pool에
할당된다. 만약 large pool이 충분하지 않으면 ORA-4031이 발생한다.
2. 사용 방법
large pool을 지정하기 위해서는 init.ora file 내에 large_pool_size라는
parameter를 사용하고, larlge_pool_min_alloc parameter는 이 large pool에
할당될 최소한의 memory chunk size를 제한한다. 이 large_pool_min_alloc의
값이 클수록 large pool의 fragmentation은 줄어든다.
만약 이 parameter를 지정하지 않으면 large pool은 사용하지 않는다. 그러나 다음
중 하나라도 만족되는 상황에서는 large pool에 관한 parameter가 설정되어 있지
않다 하더라도 Oracle이 자동으로 필요한 large pool을 계산하여 할당하여 사용한다.
- parallel_automatic_tuning = true
- parallel_min_servers=n
- dbwr_io_slaves=n
large pool size에 대한 계산은 다음 값에 의해서 결정된다.
- parallel_max_servers
- parallel_threads_per_cpu
- parallel_server_instances
- mts_dispatchers
- dbwr_io_slaves
이러한 default에 의해 계산된 large pool이 너무 크게 되면, performance에
문제가 생기거나 db startup이 안 될 수 있다. 그러므로 이러한 때에는 적당
한 값의 large_pool_size로 지정한 후 다시 startup하여야 한다.

LARGE POOL and RMAN

Hi,
Because I use RMAN I decided to configure Large Pool. It is said, that RMAN should use this area if it's defined. But im my system statistics for LargePool are constant - there is always only empty space, no blocks are allocated by RMAN. Could someone tell me what's wrong? Why my RMAN still uses shared pool and no large?
Regards,
Kuba

that was an interesting question, after checking in metalink this seems to be myth that if you configure large_pool rman will use it. (the problem with oracle documentation is it conveniently forgets to qualify the conditions).
"The LARGE_POOL is only used if I/O Slaves are specified by one or both of the initialization parameters DBWR_IO_SLAVES or BACKUP_TAPE_IO_SLAVES."
so in your case may be you have not using these parameters, that maybe the reason why RMAN is not using Large_pool.
check metalink note : 134214.1 for more RMAN myths.
which leaves us wondering...why can't these information be made available in the public documentation in the form of short notes or caveats???

Calculating Large Pool value

Hi,
I need to determine the 'large pool' size to be implemented for using RMAN. (We already have RMAN running). I need to know what parameters I need to set in init.ora for large_pool to work efficiently in conjunction with RMAN. How do I calculate the required size. I found some material on this, here, but it's confusing.
By default LARGE POOL = 0, unless PARALLEL_AUTOMATIC_TUNING = TRUE, (in which case LP will be set automatically). Also, set LARGE_POOL_MIN_ALLOC to a non-zero value to enable a minimum allocation with LP.
When I read document (ID 73079.1) it gets more confusing, as whether to take MULTIBLOCK-READ-COUNT value or DB_FILE_DIRECT_IO_COUNT into consideration. Also, what is the number of datafiles, (is it the same as db_files in init.ora ??)
Thanks in advance, Sreedhar
[email protected]
null

Hi ...
Take care about use LARGE_POOL if your database also use MTS . All MTS services will be deployed at the large_pool.
Just consider it ...
Regards,
Jose Ramon

Large pool usage and advanced queueing

Hello All,
I'm using Oracle 10.2.0.3 under Linux IA 32Bits.
I've got a big problem with my large pool that keep increasing as I'm using Advance queuing. After a while, errors 4031 are raised.
Can someone explain how to monitor large pool usage. Espaecially I would like to know wich process/ session consumes large pool.
Thanks in advance for your help

Whilst Daniel does his 'Twenty Questions' trick on you (he has a valid point: OS and Oracle Version are ALWAYS useful to know... but there's no need to pin it down to four decimal places for such a simple question!), I'll have a go at actually providing an answer.
A number of things might be going on.
First, do a google search on "joxs heap init" and you'll find suggestions that setting or increasing the JAVA_POOL_SIZE can fix the problem. See this for example, which has exactly your problem:
http://www.mail-archive.com/[email protected]/msg36154.html
Second, a lot of things that would use the Large Pool if it exists can instead make use of the shared pool if it doesn't -but they fragment the thing mightily as they do (the Large Pool was invented precisely to provide a chunk of memory that doesn't age out, only gets re-used and thus never fragments). So something (an RMAN backup, for example) might work without a large pool, if there's room in the shared pool; but if the shared pool is already fragmented or tight, then it will error with a 4031. Allocate it a bit of Large Pool, however, and it prefers to use that, finds the memory it needs is now available and therefore works fine.
The large pool is used for RMAN, shared server, I/O slaves and parallel slaves. Who knows precisely what's going on in an export that might be touching on at least 2 of those things without you explicitly asking for it to do so?! I mean that it's possible it's doing a bit of 'internal parallelism' to make itself efficient, for example, and failing to find the memory it needs for inter-parallel-slave communications. Just a possibility and a bit of speculation on my part.
I suppose the next experiment would be: take Large Pool back down to zero and then set Java Pool to 15M instead (note you should really be allocating in units of 4M these days, though Oracle will round up anyway).

Large pool and AQ

Hello All,
I'm using Oracle 10.2.0.3 under Linux IA 32Bits.
I've got a big problem with my large pool that keep increasing as I'm using Advance queuing. After a while, errors 4031 are raised.
Can someone explain how to monitor large pool usage. Espaecially I would like to know wich process/ session consumes large pool.
Thanks in advance for your help

that was an interesting question, after checking in metalink this seems to be myth that if you configure large_pool rman will use it. (the problem with oracle documentation is it conveniently forgets to qualify the conditions).
"The LARGE_POOL is only used if I/O Slaves are specified by one or both of the initialization parameters DBWR_IO_SLAVES or BACKUP_TAPE_IO_SLAVES."
so in your case may be you have not using these parameters, that maybe the reason why RMAN is not using Large_pool.
check metalink note : 134214.1 for more RMAN myths.
which leaves us wondering...why can't these information be made available in the public documentation in the form of short notes or caveats???

Look into the Large Pool

Can some one told me , how to check Large pool inside.
Why Large pool is using more memory.
Which processes are running in the Large Pool

Hi,
The V$SGASTAT dynamic performance view has a column called POOL. It is used to contain the pool area where that particular type of object is being stored. By issuing a summation select against the V$SGASTAT view, a DBA can quickly determine the size of the large pool area currently being used.
SELECT name, SUM(bytes) FROM V$SGASTAT WHERE pool='LARGE POOL' GROUP BY ROLLUP(name);
Sizing the large pool can be complex. The large pool, if configured, must be at least 600 kilobytes in size. Usually, for most MTS applications, 600 is enough. However, if PQO (parallel query option) is also used in your Oracle8,Oracle8i, or Oracle9i environment, then the size of the large pool will increase dramatically.
The V$SGASTAT dynamic performance view has a new column in Oracle8 called POOL. It is used to contain the pool area where that particular type of object is being stored. By issuing a summation select against the V$SGASTAT view, a DBA can quickly determine the size of the large pool area currently being used.
Hope this helps. . .
Don Burleson
Oracle Press author

Large pool processess

hai
For what type of I/O server processess the large pool is being used.

Hi,
On documentation, the large pool allocation heap is used in shared server systems for session memory, by parallel execution for message buffers, and by backup processes for disk I/O buffers.
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams090.htm#sthref379
Cheers

Large pool size

Hi, how to resolve the problem ORA-04031 my SGA is
504439252
455124
478150656
25165824
667648
java_pool_size 159383552
large_pool_size 16777216
shared_pool_reserved_size 10485760
shared_pool_size 209715200
This problem occurred when export full the DB

hi froylan,
this is the portal content management forum. for your database question please use the database forums:
http://forums.oracle.com/forums/index.jsp?cat=18
thanks,
christian

Shared pool request_failures

Hello,
Does any one ever faced the problem of REQUEST_FAILURES in shared pool? If yes, please share your experience(s). We have this issue every now and then, and I am just fed up of this alarm. Sometimes request_failures are over thousand.
This occurs in both 10g (10.2) and 11g DB (11.2.0.3) OS=RHL data guard setup
SYS@db AS SYSDBA> select request_failures from v$shared_pool_reserved; ---Primary DB
REQUEST_FAILURES
           52
SYS@db AS SYSDBA> show parameter shared_pool_reserved_size
NAME                         TYPE                           VALUE
shared_pool_reserved_size          big integer                      348966092
SYS@db AS SYSDBA> select free_space,avg_free_size,used_space,request_failures,requests,max_free_size,request_misses from v$shared_pool_reserved;
FREE_SPACE AVG_FREE_SIZE USED_SPACE REQUEST_FAILURES   REQUESTS MAX_FREE_SIZE REQUEST_MISSES
236005496    241314,413    5668264            57           0       6713160             0Thanks a lot.
Best Regards
Edited by: K-Saf on Sep 4, 2012 12:46 PM
Edited by: K-Saf on Sep 4, 2012 12:46 PM
Edited by: K-Saf on Sep 4, 2012 1:00 PM

Hello Kuljeet Pal,
Thanks a lot. Here is the result of your suggested queries. Please have a look and suggest.
- AS SYSDBA> SELECT shared_pool_size_for_estimate, estd_lc_size, estd_lc_time_saved FROM v$shared_pool_advice;
SHARED_POOL_SIZE_FOR_ESTIMATE ESTD_LC_SIZE ESTD_LC_TIME_SAVED
                2816            455            819115
                3584           1222            819732
                4352           1990            824577
                5120           2758            837826
                5376           3014            848912
                5504           3142            854454
                5632           3270            860003
                5760           3398            865548
                5888           3526            871084
                6016           3653            876620
                6144           3780            882158
                6272           3908            887700
                6400           4036            893245
                6528           4164            898789
                6656           4292            904342
                6784           4420            904351
                6912           4548            904351
                7040           4676            904352
                7168           4804            904353
                7296           4932            904354
                7424           5060            904355
                7552           5188            904356
                7680           5316            904356
                7808           5444            904356
                8192           5828            904356
                8960           5888            904356
                9728           5888            904356
               10496           5888            904356
               11264           5888            904356
               12032           5888            904356
               12800           5888            904356
               13568           5888            904356
32 rows selected.
COMPONENT                 OPER_TYPE       PARAMETER                INITIAL_SIZE TARGET_SIZE FINAL_SIZE STARTED                                                              ENDED
streams pool                 GROW            streams_pool_size           134217728   268435456     268435456 03-sep-2012:14:07:44                                                         03-sep-2012:14:07:44
DEFAULT buffer cache            SHRINK            db_cache_size               3,4226E+10 3,4091E+10 3,4091E+10 03-sep-2012:14:07:44                                                         03-sep-2012:14:07:44
java pool                 STATIC            java_pool_size                     0   134217728     134217728 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
streams pool                 STATIC            streams_pool_size                0   134217728     134217728 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
DEFAULT buffer cache            INITIALIZING    db_cache_size               3,4226E+10 3,4226E+10 3,4226E+10 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:31
ASM Buffer Cache            STATIC            db_cache_size                     0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
DEFAULT buffer cache            STATIC            db_cache_size                     0 3,4226E+10 3,4226E+10 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
DEFAULT 2K buffer cache        STATIC            db_2k_cache_size                 0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
DEFAULT 4K buffer cache        STATIC            db_4k_cache_size                 0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
DEFAULT 8K buffer cache        STATIC            db_8k_cache_size                 0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
DEFAULT 16K buffer cache       STATIC            db_16k_cache_size                0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
DEFAULT 32K buffer cache       STATIC            db_32k_cache_size                0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
KEEP buffer cache            STATIC            db_keep_cache_size                0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
RECYCLE buffer cache            STATIC            db_recycle_cache_size                0          0          0 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
shared pool                 STATIC            shared_pool_size                 0 6979321856 6979321856 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
large pool                 STATIC            large_pool_size                     0   134217728     134217728 30-aug-2012:15:31:27                                                         30-aug-2012:15:31:27
16 rows selectedBest Regards

Issue with shared pool size while upgrading from 10.2.0.4 to 11.2.0.2

Hi Team,
Below is my issue
I am running dbua as part of the upgrade from 10.2.0.4 to 11.2.0.2. Its almost 59% and nothing is happening on the instance. The logs directory contian the below
-bash-3.00$ ls -ltr
total 280
-rw-r----- 1 ora8014 ems8014 3662 Oct 16 08:58 upgrade.xml
-rw-r----- 1 ora8014 ems8014 1127 Oct 16 09:00 Upgrade_Directive.log
-rw-r----- 1 ora8014 ems8014 7452 Oct 16 09:00 mapfile.txt
-rw-r----- 1 ora8014 ems8014 297 Oct 16 09:04 SpaceUsage.txt
-rw-r----- 1 ora8014 ems8014 9803 Oct 16 09:04 PreUpgradeResults.html
-rw-r----- 1 ora8014 ems8014 1572 Oct 16 09:06 PreUpgrade.log
-rw-r----- 1 ora8014 ems8014 2850 Oct 16 09:06 Oracle_Text.log
-rw-r----- 1 ora8014 ems8014 157816 Oct 16 09:09 trace.log
-rw-r----- 1 ora8014 ems8014 71368 Oct 16 09:09 sqls.log
-rw-r----- 1 ora8014 ems8014 339 Oct 16 09:09 Oracle_Server.log
-bash-3.00$ date
Sat Oct 16 22:54:27 PDT 2010
-bash-3.00$ pwd
/slot/ems8014/oracle/app/ora8014/cfgtoollogs/dbua/ebs11i10/upgrade1
It seems its almost more 12 hrs nothing has happened. When I check the oracle_server.log it has the error
-bash-3.00$ tail Oracle_Server.log
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
select count(*) from v$instance
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
ORA-00371: not enough shared pool memory, should be atleast 424463564 bytes
Hence I started the Db in 10g oracle home to check and below is the details.
SQL> select * from V$SGAINFO;
NAME BYTES RES
Fixed SGA Size 1267908 No
Redo Buffers 11313152 No
Buffer Cache Size 614400000 Yes
Shared Pool Size 301989888 Yes
Large Pool Size 8388608 Yes
Java Pool Size 67108864 Yes
Streams Pool Size 50331648 Yes
Granule Size 4194304 No
Maximum SGA Size 1056964608 No
Startup overhead in Shared Pool 188743680 No
Free SGA Memory Available 0
11 rows selected.
I tried to increase the space of shared pool as below
SQL> ALTER SYSTEM SET shared_pool_size ='301M' SCOPE=MEMORY SID='ebs11i10';
ALTER SYSTEM SET shared_pool_size ='301M' SCOPE=MEMORY SID='ebs11i10'
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-04033: Insufficient memory to grow pool
I am stuck and cant proceed further. Could you please help me on this issue so that I overcome this and proceed further.
Thanks
Shyam.

These are the logs. Could you please let me know which one you want.
-bash-3.00$ pwd
/slot/ems8014/oracle/app/ora8014/cfgtoollogs/dbua/ebs11i10/upgrade1
-bash-3.00$ ls -ltr
total 280
-rw-r----- 1 ora8014 ems8014 3662 Oct 16 08:58 upgrade.xml
-rw-r----- 1 ora8014 ems8014 1127 Oct 16 09:00 Upgrade_Directive.log
-rw-r----- 1 ora8014 ems8014 7452 Oct 16 09:00 mapfile.txt
-rw-r----- 1 ora8014 ems8014 297 Oct 16 09:04 SpaceUsage.txt
-rw-r----- 1 ora8014 ems8014 9803 Oct 16 09:04 PreUpgradeResults.html
-rw-r----- 1 ora8014 ems8014 1572 Oct 16 09:06 PreUpgrade.log
-rw-r----- 1 ora8014 ems8014 2850 Oct 16 09:06 Oracle_Text.log
-rw-r----- 1 ora8014 ems8014 157816 Oct 16 09:09 trace.log
-rw-r----- 1 ora8014 ems8014 71368 Oct 16 09:09 sqls.log
-rw-r----- 1 ora8014 ems8014 339 Oct 16 09:09 Oracle_Server.log

Create a spatial index on a large table

Hi all
I think that I might be starting to push XE beyond what it is capable of, but I thought I would ask here to see if anyone has some ideas how to get around my problem.
I have a table with around 8,000,000 record in it. It has position data in it (SDO_GEOMETRY) which I would like to index. The geometry is not complex, just a single point for each record. The SQL I use is
CREATE INDEX "ANNOTATION_TEXT_SX" ON "ANNOTATION_TEXT" ("GEOLOC") INDEXTYPE IS "MDSYS"."SPATIAL_INDEX"
The command fails, due to memory issues. The errors thrown are
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13236: internal error in R-tree processing: [failed to cluster in memory]
ORA-13232: failed to allocate memory during R-tree creation
ORA-13236: internal error in R-tree processing: [failed to allocate memory 7272216 (mdrtsalloc)]
ORA-04031: unable to allocate ORA-04031: unable to allocate 7272264 bytes of shared memory ("lar
I have done a bit of reading up, this type of error generally occurs when the tablespace runs out of memory. Since I am using the SYSTEM tablespace, I figure I am running it out to its capacity before the index is completed.
I have not created any other tablespaces. Is this an option to allow the creation of the index? Storage and Memory are at about 60% capacity (due to this one table) so is it just too big to create a spatial index on in XE? Am I barking up the wrong tree?
Cheers
James

Good to see you are not using the SYSTEM tablespace. (And no need to apologize too profusely for being new at this - we all were at one time.)
It normally doesn't matter how many rows are involved. The issue is how much actual space those rows require. 8,000,000 rows is actually not a lot in the GIS world, esp. if all you have is simple point data. Using the sdo_point field instead of the arrays should be a lot more compact as well.
Some steps I would take:
- Identify the actual amount of space used, in total as well as by tablespace. (One of the web-based admin screens can show you this.)
- Load it all up usnig the free 'developer license' Enterprise Edition insead of XE just to verify it'll work.
- Try indexing a smaller data set and see whether that works. (Export the table first) Delete about 1/2 rows and try indexing.
The ORA-04031 is really telling you something about the SGA is not big enough. One of the SGA pools is trying to extend by 7M. Post the info about your SGA, as well ass some details about your machine (disk/processor/total memory)
Message was edited by:
forbrich
The actual error causing the problem is the last line. It ends with "la and the rest is cut off. Could it have said 'large pool'???

SGA_MAX_SIZE and SGA_TARGET how to set minimum for pools

Hello, we are on 10.2.0.4, Solaris 5.10. We are using ASMM, so SGA_TARGET and SGA_TARGET size are set. Hence, buffer cache, shared pool, large pool and java pool are automatically sized. However, we do not have any minimum values for those. How do I determine what this minimum value should be?
thank you!

HI,
Yes you need size the minimum value for shared pool, buffer cahce tec... else it will start consuming wholeThe documentaion
states:
You need not set the size of any of these components explicitly. By default the parameters for these components will appear to have values of zero. Whenever a component needs memory, it can request that it be transferred from another component by way of the internal automatic tuning mechanism. This transfer of memory occurs transparently, without user intervention.Can you please explain how would it start consuming the entire SGA?

LDAP Performance Tuning In Large Deployments - dir_chkcredentialsonreadonly parameter

Calendar users are experiencing long delays in logging in or updating a meeting
with many attendees or dates. This is especially notificeable after migrating
from calendar server 1.0x to calendar server 3.x.

At this time, calendar performance can be improved by up to 30% by reconfiguring
the calendar server to bind to it's directory server either anonymously or with
a specific user. The default is to bind as the user requesting directory
information.

There is a parameter that can be added in the server configuration file by
editing the /users/unison/misc/unison.ini file. For anonymous binds
adding the dir_chkcredentialsonreadonly line to the DAS section:

[DAS]
dir_updcalonly = TRUE
dir_connection = persistent
dir_service = LDAP,v2,NSCP,1
enable = TRUE
dir_chkcredentialsonreadonly = FALSE

For binding as a specific user, also add the following to the LDAP,..,...,,
section:

[LDAP...]
binddn = dn
bindpwd = password

Going forward, we are working on other changes in the next versions of the
Calendar Client and Calendar Server to improve performance. Please check with
your Netscape Sales contact for announcements on the availability of these
versions.


Thank you very much, I am looking from now for a good performance Tuning book writen by Jonathan Lewis. I dont think Jonathan can come to Spain and give lessons...Anyway I will email to him...
But, could you please clarify 2 points to me
1- Should I modify manually memory parameters like buffer cache, shared pool, large pool etc...if those areas are spotted Small and areas causes of performace problem in the AWR, ADDM or ASH reports even if the memory is automatic managed ?
In the case of yes, Why Oracle named it "Memory automatic managed" if I have to set some values of memory manually ?
2- When ADDM report suggests me to increase the SGA size; from where ADDM got this recomandation?. I mean is it recomandation based on statistics collected of Both Oracle and OS ? I am asking this question because, from our report I ran 3 weeks ago, ADDM suggested me to increase the SGA to 10GB (total memeory of the serve is 16GB), I did the change and from that moment the server is SWAP... and now ADDM report suggests me again to increase the SGA to 12GB .
Best reagards

Large pool or shared_pool_reserved_size

Similar Messages

Maybe you are looking for