Re: OPS and LK_STAT_MAXLOCK errors

In article <01be3fe8$18c99820$51630c8a_at_creinja-nt>,   "Jeff Reineke" <jeffrey.reineke_at_lexis-nexis.com> wrote:
> Thanks for your help. We've increased both of these parameters based on
> some calculations from Oracle documentation but we still hit the limit on
> maxlocks. Do you have any advise of how high to set these?
>
> Jeff Reineke
>
> mgogala_at_rocketmail.com wrote in article
> <77jfdk$ptb$1_at_nnrp1.dejanews.com>...
> > In article <01be3f3c$c32ce6c0$51630c8a_at_creinja-nt>,
> > "Jeff Reineke" <jeffrey.reineke_at_lexis-nexis.com> wrote:
> > > Has anyone had problems receiving the LK_STAT_MAXLOCK error from the
> > > distributed lock manager using OPS? We found some calculations for
> > > maxlocks from Oracle, but still seem to reach the max locks limit. Is
> > > there anything else that can cause this error?
> > >
> > > Jeff Reineke
> > > LEXIS-NEXIS
> > >
> > Insufficient number of DLM locks configured on the OS level.
> > On SUN, there is a file under /etc/opt where you can configure number
> > of locks. I called Oracle Support once, and they told me to increase the
> > number of locks as long as I'm getting this errors. The other error
> > you are likely to get is LK_STAT_MAXRES error, which informs you that
> > you should increase the number of DLM resources as well.
> >
> > Mladen Gogala
> >
> > -----------== Posted via Deja News, The Discussion Network ==----------
> > http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
> >
>

Take the numbers you've got from Oracle formulas and multiply them by 3 (all of them.) You'll end up wid 250MB of RAM in your dlmd, but it's going to be stable. And if you are using SUN, I sincerely recommend setting the parameter _enable_dba_locking=TRUE. Mladen Gogala

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Thu Jan 14 1999 - 19:47:20 CST