Re: DLPAR and Memory
- From: "Dave" <dacooley@xxxxxxxxx>
- Date: 8 Mar 2006 08:28:27 -0800
Funny this should come up... we just went through this last week...
It appears that in the default oracle settings with 9i, it allocates
the maximum real memory it finds for SGA... then, as connections come
in and oracle has to spawn new processes off, there is no more real
memory to operate in (since it "pre-allocated" it) and it begins
swapping like mad, eventually bringing the server to it's knees. Our
DBA had to set the SGA to use a fixed amout of memory, and now the
servers run perfectly.
so, make sure to set SGA_MAX_SIZE to some reasonable amount.
The other problem you can run into is if Oracle has set the *_AREA_SIZE
params (sort, hash etc) individually... if so, then each user is
allocated those size chunks individually, even if they are not used...
if you set the PGA_AGGREGATE_TARGET to say 4GB, then you limit the
total area size used to that one chunk, and all users share it, only
using what they need for their transactions then releasing it back to
the pool.
.
- References:
- DLPAR and Memory
- From: flossyfloss
- DLPAR and Memory
- Prev by Date: DLPAR and Memory
- Next by Date: Re: Error after installing AIX 5.3
- Previous by thread: DLPAR and Memory
- Next by thread: Re: DLPAR and Memory
- Index(es):
Relevant Pages
|
