resident memory of an Oracle process

[Joseph Hoh]

We have an Oracle process that will run for approx. 24hours and then die with an "out of memory" message. I have noticed that the resident memory of the process will increase to approx. 265000KB and then die. When the process runs successfully it only goes up to about 90000KB of resident memory. The system has approx 8GB of memory and does not appear to be swapping. Is there a limit on resident memory per process. I have a hunch that there is something different in the database or the application but I have to prove something from the system side first. No other databases are having problems. We have approx. 30 dbs on this system. Any help would be appreciated.

[Alexander M. Ermes]

Hi there.
You should check the system global area of your database.
Parameters in init.ora :

db_block_buffers
sort_area_retained_size
sort_area_size

shared_pool_size
# This gives the memory for your instance. Increase might help.
There were limitations on 32-bit systems to a SGA of 1.75 GB overall, but i think you run a 64-bit version of the database.

Rgds
Alexander M. Ermes

[Praveen Bezawada]

Hi
From OS side I think you need to check the value of maxdsiz, maximum data segment size for 64 BIT system it's maxdsiz_64.
Increase the value of maxdsiz or maxdsiz_64bit if you have one or more processes that use large amounts of data. And also check the size of dbc_max_pct,The value of dbc_max_pct sets the maximum percentage of physical memory that can be allocated to the dynamic buffer cache.

...BPK...

[Wodisch]

Hello Jeff,

I would also recommend to check your free swap space
while that command is running! As on HPUX even the
shared memory needs swap space, take care to have
your kernel have some free entries for the parameter
"max_swap_chunks"

Just my ?0.02,

Wodisch