MAXUSERS is like using a shotgun to kill a cockroach. Now granted,
being from the south I have seen some big cockroaches. However, if
you have a file table overflow, address the parameter that deals with
the file table (nfile) and let the other sleeping dogs lie. MAXUSERS,
in my opinion, is a formula provided for administrators who don't have
a really good idea about what is going on in the kernel. The only
thing worse than maxusers is applying tuned parameter sets.
HP_BRS
violin.hsiao_at_mail.pouchen.com.tw (Violin) wrote in message news:<d22954a4.0205061907.35ed1d1d_at_posting.google.com>...
> Thanks for you all,
> You're so kind to help me to solve this urgent problem.
> I'm sorry for cross-posting.
>
> From Oracle metalink , we've found a doc for this issue and we changed
> kernel again, Now the instance is running normally.
>
> Thank you all.
>
> Violin.
>
> Article-ID: <Note:68105.1>
> Circulation: PUBLISHED (EXTERNAL)
> Folder: platform.Unix.HPUX
> Topic: Configuration
> Title: Commonly Misconfigured HP-UX Kernel Parameters
> Open-Remarks: See <RemarksOn:NOTE:68105.1>
> Document-Type: BULLETIN
> Impact: MEDIUM
> Skill-Level: NOVICE
> Updated-Date: 21-MAY-2001 09:14:39
> References:
> Shared-Refs:
> Authors: KSHERGIL.UK
> Attachments: NONE
> Content-Type: TEXT/PLAIN
> Products: 5;
> Platforms: 2;
>
> PURPOSE
>
> This note lists commonly misconfigured HP-UX kernel parameters.
>
> @ A lot of the info is taken from the HP/Oracle CTC (internal) website
> at
> @ http://www.hporaclectc.com
>
> parameter | default | recommended | notes
> ======================================================================
> aio_max_ops | 2048 | 2048 | max no of queued AIO ops
> | | | See Note:139272.1
> ----------------------------------------------------------------------
> dbc_min_pct | 5 | 2 | min %age of system mem
> used
> | | | for buffer cache
> | | | (valid if nbuf = bufpages
> = 0)
> ----------------------------------------------------------------------
> dbc_max_pct | 50 |ensure <= 128MB | max %age of system mem
> used
> | |used as cache | for buffer cache
> | | | (valid if nbuf = bufpages
> = 0)
> | | | Also see Note:62589.1
> ----------------------------------------------------------------------
> fsasync | 0 | 0 | async i/o on filesystems
> | | | See Note:139272.1
> ----------------------------------------------------------------------
> max_async_ | 50 | see notes | See Note:139272.1
> ports | | |
> ----------------------------------------------------------------------
> maxdsiz | 64MB | >=128MB | shadow process' heap size
> maxdsiz64 | 1GB | 1GB |
> ----------------------------------------------------------------------
> maxfiles | 60 | >= 512 | soft limit
> | | | no of open files per
> process
> ----------------------------------------------------------------------
> maxfiles_lim | 1024 | 1024 | hard limit
> | | | no of open files per
> process
> -----------------------------------------------------------------------
> maxusers | 32 | no of Oracle | influences nproc, nfile,
> | | connections+64 | ninode, maxuprc
> ----------------------------------------------------------------------
> maxuprc | 50 | maxusers*5 | no of procs per userid
> ----------------------------------------------------------------------
> nfile | | use SAM formula | open files system wide
> ----------------------------------------------------------------------
> nflocks | 200 | >= (200 + | file locks system wide
> | |(sum of db files | 8i onwards uses o/s file
> locking
> | |for all instances| undersizing will give
> | |) | HP-UX Error: 46: No locks
> available
> | | ) |
> ----------------------------------------------------------------------
> nproc | | use SAM formula | processes system wide
> ----------------------------------------------------------------------
> shmmax | | see notes | >=0x100000000 (267MB) for
> 64bit RDBMS
> | | | >=0x2000000 (34MB) for
> 32bit RDBMS
> | | | undersizing gives
> ORA-00600 [SKGMINVALID]
> ----------------------------------------------------------------------
> swapmem_on | 0 | see notes | see Note:68056.1
> ----------------------------------------------------------------------
>
>
> dfreybur_at_yahoo.com (Doug Freyubrger) wrote in message news:<7960d3ee.0205061059.373d610b_at_posting.google.com>...
> > Violin wrote:
> > >
> > > We're running Oracle 8.1.7 on HP-UX 11.0.
> > > Today there are too many connections,so the database instance crushed.
> > > HP-UX Error: 23: File table overflow
> > >
> > > We got HP-UX Error:23:File table overflow before,and tried to resolve
> > > this by increase maxusers value.
> > >
> > > The value of maxusers now is 250, but today when I increase the value
> > > over than
> > > 251 , I got the error message in sam monitor:
> > > The parameter modification(s) you have made have resulted in at
> > > least one parameter evaluating to a value which is greater
> > > than its maximum allowable value. Parameter "msgseg", currently
> > > set to "(MSGTQL*4)", has evaluated to "32800",which is greater
> > > than its maximum allowable value of "32767".
> >
> > I recently had to tune an HP-UX 11i server in 2 or 3 steps because
> > of similar limits. Look at the value for maxusers. Is it a
> > formula? If so start by modifying what it points to. Look at all
> > of the other values one by one. Look for any that are formulas
> > that use maxusers (there will be several). You will need to change
> > those first, or at the same time.
> >
> > I selected some that were a formula based on maxusers, discovered
> > their max allowed values, set them to those values numerically so
> > they were no longer formulas based on maxusers, then changed
> > maxusers.
Received on Wed May 08 2002 - 06:57:21 CDT
