Kernel parameters SAM

[jamshed]

For installing Oracle 9i on my server I have to change kernel configuration parameter, but some parameters did not appear on my screen (SAM). How can I restore those parameters? Those parameters write on /stand/system file, but I canâ t see it on SAM (kernel configuration paramete

[Joseph Loo]

hi,

what are the kernel parameters missing from SAM? by the way, could you do reply the output for this:

#getconf HW_CPU_SUPP_BITS

regards.

[Steven E. Protter]

My best guess is that you need to restore your system file.

All configurable parameters that show up in kmtune should be in the sam kernel screen.

SEP

[Jakes Louw]

Be very careful of parameters that "don't appear on SAM": some params are obsolete on 11i, and will NOT appear on SAM. Attempting to set these params manually using an edited version of the source files can cause MAJOR trouble if you enable the wrong params.

Which params are you specifically talking about?

[jamshed]

How can i restore my system file?

[Elmar P. Kolkman]

To restore the system file to the version used by SAM, copy the SAM version over the /stand version:
cp /stand/build/system.SAM /stand/system

First check for differences.... I have systems with lots of them and then you might run into problems.
Perhaps using sysdef to get the current parameters is a better solution...

[D.Blond]

Hi,
For installing Oracle 9i on my server hpux 11.00 or 11.11, I have changed kernel parameters in joined file.
regards

[jamshed]

#getconf HW_CPU_SUPP_BITS
64

[John Carr_2]

Hi

to get a new system file based on the configuration in the kernel

/usr/lbin/sysadm/system_prep -s system

:-) John.

[jamshed]

After running this command
# /usr/lbin/sysadm/system_prep -s system
System file was recreated but I saw difference between system file and kmtune command listing.

[John Carr_2]

Hi

can you tell me which differences you wish to investigate please.

John.

[John Carr_2]

jamshed

I think what may be happening is that first you are looking at the true kernel parameters which are running from the new system file you have created.

Some parameters are Dynamic meaning the kernel can be dynamically updated using kmtune. If some changes have been made using kmtune and kmsystem but a kmupdate has not been executed differences may occur in the listings.

kmupdate /stand/build/vmunix_test
cd /
shutdown -ry now

John.

[Jakes Louw]

I don't see any problems with what you have sent. If the specific param is not in the system file, that simply means that the default value will be used.

Get the doc "Tunable Kernel Parameters, HP-UX Release 11i", I think you can search ITRC for part number TKP-90202.

[jamshed]

KSI_ALLOC_MAX
MAX_THREAD_PROC
MAXDSIZ
MAXDSIZ_64
MAXSSIZ
MAXSSIZ_64BIT
MAXSWAPCHUNKS
MAXUPRC
MSGMAP
MSGMNI
MSGSEG
MSGTQL
NCALLOUT
NCSIZE
NFILE
NFLOCKS
NINODE
NKTHREAD
NPROC
SEMMAP
SEMMNI
SEMMNS
SEMMNU
SEMVMX
SHMMAX
SHMMNI
SHMSEG
VPS_CEILING
-- here kernel parameters for installing Oracle 9i but i can't find them in my HP-UX 11.00 kernel parameters.

[jamshed]

How can I find my tunable kernel parameters?
For example (NPROC, SEMMAP, SEMMNI, SEMMNS â ¦) this parameter is not present on my system file or SAM kernel configuration

[Jakes Louw]

As I mentioned above, get the doc I mentioned.
To answer you:
NPROC - default is (20+8*maxusers), allowed values between 10 and 30000. Specifies the limit of the number of processes that may run SIMULTANEOUSLY.If this is set too low, messages like "proc:table is full" and "unable to fork" will be seen in syslog and dmesg.

SEMMAP - default is (semmni + 2). See the default for SEMMNI below. Minimum=4, max is less than or equal to 32767. Specifies the number of entries in a System V IPC semaphore map.

SEMMNI - default is 64. Minimum = 2, max = semvmx. Specifies the number of System V IPC system-wide semaphore identifiers. Therefore SEMMAP must ALWAYS be less than SEMMNI.

SEMMNS - default is 128. Minimum = 2, max = 32767. Specifies the number of System V IPC system-wide semaphores. Think of SEMMNI being a pointer to SEMMNS, so these two params should always be the same.

Read the sema(5) manpage for more info.