Sys-Admin Information’s

Share Knowledge, Distribute Knowledge, Capture & Modify Knowledge, Create Knowledge

Archive for the ‘Tunable Parameters’ Category

Comparison Kernel parameter Solaris9 and Solaris10

with 2 comments

SERVER – Solaris9 – Oracle9i …..[compare]….. SERVER – solaris10 – Oracle10g

[ Solaris9] forceload:sys/shmsys
[Solaris10] recommended not set, server impact long time for boot up

[ Solaris9] forceload:sys/semsys
[Solaris10]recommended not set, server impact long time for boot up

[ Solaris9] set shmsys:shminfo_shmmax=51539607552
[Solaris10] projmod -s -K “project.max-shm-memory=(priv,48g,deny)” user.oracle

[ Solaris9] set shmsys:shminfo_shmmin=1
[Solaris10] Obsolete in the Solaris 9 release, Solaris 10 also

[ Solaris9] set shmsys:shminfo_shmmni=2048
[Solaris10] projmod -s -K “project.max-shm-ids=(priv,2048,deny)” user.oracle

[ Solaris9] set shmsys:shminfo_shmseg=200
[Solaris10] Obsolete in the Solaris 9 release, Solaris 10 also

[ Solaris9] set semsys:seminfo_semmni=1000
[Solaris10] projmod -s -K “project.max-sem-ids=(priv,1000,deny)” user.oracle

Read the rest of this entry »

Written by Hell-me

March 4th, 2008 at 6:27 pm

Change SHMMAX without rebooting

with 2 comments

Shmmax parameter is supposed to be the maximum size of a single shared memory segments (and the oracle sga is build out of these shared memory segments).

New to the Solaris 8 release is the modular debugger, mdb(1), which is unique among
available Solaris debuggers because it is easily extensible. Mdb(1) also includes a number of desirable usability features including command-line editing, command history, built-in output pager, syntax checking, and command pipelining. This is the recommended post-mortem debugger for the kernel.

To change the value of the integer variable shmmax from 8GB to 10 GB without Reboot Server, do the following

bash> cp /etc/system /etc/system_old
bash> grep shminfo_shmmax /etc/system
set shmsys:shminfo_shmmax=8589934592
bash> mdb -k
Loading modules: [ unix krtld genunix ip usba s1394 ipc nfs ptm logindmux random ]
> shminfo_shmmax /D
shminfo_shmmax:
shminfo_shmmax: 1
> shminfo_shmmax /E
shminfo_shmmax:
shminfo_shmmax: 8589934592
> $q

At we can see the “shminfo_shmmax” use a 64 bit value, let’s start to change the value

bash> mdb -kw
Loading modules: [ unix krtld genunix ip usba s1394 ipc nfs ptm logindmux random ]
> shminfo_shmmax /Z 0t10737418240
shminfo_shmmax: 0x5f5e10000             =       0x19000
> shminfo_shmmax /E
shminfo_shmmax:
shminfo_shmmax: 10737418240
> $q

After successfully, change the parameter “shminfo_shmmax” at /etc/system with same value on mdb

bash> vi /etc/system
set shmsys:shminfo_shmmax=10737418240

Written by Hendrawan

February 21st, 2008 at 5:26 pm