Re: paging, minperm and maxperm

Hi David,

I'm not a great liker of rules of thumb but as a roughy, Oracle should ideally use only 50% or so of available memory.

Based on the few parameters you've supplied, when adding all the various memory components you are going way over this recommendation. By increasing the memory parameters, you are probably worsening the problem, not fixing it.

Go the other way and reduce your memory parameters (1G for the buffer cache sounds totally inappropriate based on your spec). Stop the paging and performance will hopefully improve.

Do you know how to determine appropriate values for your shared pool, large pool, buffer caches, redo log buffer and so on. If not, then a DB tuning course would be of definite value (or check out the Performance Tuning guide) for some recommendations.

Good luck

Richard
"David Wang" <ywang_at_adelphia.net> wrote in message news:H6409.7859$C44.2553250_at_news2.news.adelphia.net...
> NEED HELP!!!
> Our 7.3.4 on AIX 4.3 with 2GB RAM. Most of jobs are batch jobs, concurrent
> users are about 10.
> I upgrade db_block_buffer to 1GB and shared_pool_size to 48MB. After
> changes, I found there is
> no improvement and one job even runs slower. I also found there are heavy
> paging when jobs start.
> Could anybody explain to me why that happened and Could I avoid paging by
> resetting "minperm"
> and "maxperm"(by through vmtune), e.g. minperm=10%, maxperm=40%, current
> values are 20%
> and 70%? Thanks in advance!!!
>
>
>
Received on Fri Jul 26 2002 - 00:00:45 CDT