Kernel Parameter SHMMIN on UX 11.0

[Tim Killinger]

We're still new to UX. In an Oracle installation document, there is a reference to the kernel param "SHMMIN".... kmtune does not list this parameter. Can anyone shed any light on this for me?

Thanks!

[Pete Randall]

Never heard of SHMMIN - maybe they're referring to SHMMNI?

"shmmni specifies the maximum number of shared memory segments
allowed to exist simultaneously, system-wide. Any shmget() system
call requesting a new segment when shmni segments already exist
returns an error (see shmget(2)). This parameter defines the number
of entries in the shared memory segment identifier list which is stored
in non-swappable kernel space. Space allocated for identifiers is
shmmni x104 bytes. "



Pete

[John J Read]

Doesn't exist. I've always ingored that when setting parameters for Oracle. Never had a problem. My understanding is that exists on other flavors of Unix.

-jr

[John Poff]

Hi,

Could it be a typo? Could they mean 'shmmni'? That one is the maximum number of allowed shared memory segments.

JP

[John J Read]

Just looked it up.. Solaris has this parameter. Shared Memory Mininum. It's not on HP-UX.

[Helen French]

HP-UX has no such parameter, but Sun has it. This was discussed so many times before in this forums. Check some of them:

http://forums.itrc.hp.com/cm/QuestionAnswer/0,,0x3a41ec08252fd611abd50090277a778c,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xa76a37f45ef7d4118fef0090279cd0f9,00.html

[David_246]

Who John,

You're telling oracle forgot to mention it is not for HP-UX. Never would expect it from Oracle.
anyway, You can look up and tune Kernel param very easily using Sam :

unset DISPLAY
sam
Kernel Configuration --> Configurable Parameters

Now you will find them, but indeed not the one you mention.


Regs David

[Tim Killinger]

Aha! Didn't think it existed... I've got a solaris document which also mentions SHMMIN, but it's in the Oracle UX document too.

Thanks everyone..

[Steven E. Protter]

Oracle is really good about handing out Solaris docs and saying "It's unix right?" It's not. If Oracle support gave you the doc, insist on an HP-UX doc.

If they say the fix works on Solaris and should work on HP-UX, ask them if they tested it on UX first, and make them test it first.

Half the time, I have to escalate the call to manager on duty, but about half the time Oracle discovers their procedure does not work or they revise the instructions for me.

SEP