kernel build foo

[jerry1]

When I tried to rebuild a new kernel with
sam when changing the parm semume and setting
it to a recommended value perscribed by
PeopleSoft:

SEMUME Same as SEMMNS semune <= semmns

semmns is equal to 8192. So tried 8192 for
semume.

The kernel get built smaller than the original
and hangs on bootup.

So I set semume from the default of 10 to 512
and the kernel builds.

Size of good and bad kernels:

18556184 vmunix.bad
27983672 vmunix.prev - Had to boot with this
to get back in.

Now I noticed that when changing some Dynamic
parms that do not require a reboot. The kernel
vmunix has gone down in size to 18556184.
I thought I had copied the vmunix.prev, after
booting up, to vmunix. ?? Copied it back again.

Anyway. I am trying to build a new kernel
with the change to maxssiz set to the
allowable max 98048:

from sysdef:

maxssiz 32768 - 0-98048

98048 x 4 x 1024 = 401604608

The kernel vmunix_test in /stand/build is small again:

18556208 vmunix_test

Which leads me to believe that it is not bootable either.
Aborted out of sam "replace and reboot" choice.

What is going on here?? By changing kernel
parms. Is it possible to have a smaller kernel
that is correct and bootable??

I have had to make several changes for oracle
9.2.0 and peoplesoft 8.44. Although I first
used the recommended kernel requirements for
oracle 10g application server. Which are high.

Inclosing current kernel parms.

[Steven E. Protter · Accepted solution]

If you do a dynamic change, you can use kmtune to save the make it permanent in the system file.

The oracle requiements must be met or the 10g Application server, which I've installed won't install.

You can reduce certain parameters and still be bootable, but remember, Uncle Oracle is hungry and needs a lot of resources.

SEP

[jerry1]

That's fine.

But what about the problem?

[Mahesh Kumar Malik]

Hi Jerry

Please refer to following paragraph from HP Doc site, where there is recommendation to change all related parameters at the SAMETIME


http://docs.hp.com/en/B3921-90010/semmns.5.html

What Other Tunable Values Should Be Changed at the Same Time?

All the System V semaphore tunables are interrelated and should not be treated as independent variables. The tunables must be evaluated as a system to ensure they reflect the application requirements. The sema tunables include semaem, semmap, semmni, semmns, semmnu, semmsl, semume, semvmx, and sysv_hash_locks. Typically, a change in the semmns tunable does not require changes to other tunables.

Regards
Mahesh