Sd/ssd max throttle in solaris 10 etc/system

Guru!
I need to add any of following lines to /etc/system file
for my new Hitachi storage (attached to the Soalris10 Box)
setsd: sd_max_throttle = 16mm
setssd:ssd_max_throttle =16
I want to know the difference between them and also how can I make sure that the parameter is added/active....?
Owais Hyder.

Hi.
Be carefull when edit /etc/system
Correct:
set sd: sd_max_throttle = 16
set ssd:ssd_max_throttle =16
Reboot require for applay changes.
For check current value:
echo "sd_max_throttle /U" |mdb -k
Docs:
http://docs.oracle.com/cd/E26505_01/pdf/E37386.pdf
ssd_max_throttle and sd_max_throttle parameters
define the maximum number of concurrent I/Os that the driver can send to the storage.
ssd - driver for FC disk
sd - driver for generic SCSI disk
Regards.

Similar Messages

Installing Oracle 9i on Solaris 10 SPARC, /etc/system vs. projects

Can anyone verify that the kernel tuning parameters that used to be set in /etc/system on Solaris 8 have any effect in Solaris 10? All the documentation I can find suggests that most (if not all) of these settings have been marked obsolete or removed in Solaris 10. It is my understanding that these settings (such as shared memory) need to be set by means of a project. If we are running with no project setup in Solaris 10 are we pretty much running "untuned" ? Thanks
Some links...
New or change parameters in Solaris 10
http://docs.sun.com/app/docs/doc/817-0404/appendixb-16?a=view
Solaris Tunable Parameters manual
http://dlc.sun.com/pdf/817-0404/817-0404.pdf

We have carried over the following parameters from /etc/system on our old Solaris 8 DB servers. We just want to know if these settings are having any effect. We are currently seeing some performance issues on T5220's with 32GB RAM (old DB servers were SunFire 4800's).
shmsys:shminfo_shmmax obsolete as of Solaris 10
shmsys:shminfo_shmseg removed in Solaris 10
shmsys:shminfo_shmmin removed in Solaris 10
shmsys:shminfo_shmmni obsolete as of Solaris 10
semsys:seminfo_semmns removed in Solaris 10
semsys:seminfo_semmni obsolete as of Solaris 10
semsys:seminfo_semmsl obsolete as of Solaris 10
semsys:seminfo_semopm obsolete as of Solaris 10
semsys:seminfo_semvmx removed in Solaris 10
rlim_fd_max=8096 In the Solaris 8 version, the default is 1024. In later Solaris releases, the default is 65,536
rlim_fd_cur=1024 Still supported
noexec_user_stack Still supported
Actual /etc/system settings...
set shmsys:shminfo_shmmax=31457280000
set shmsys:shminfo_shmseg=16
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=128
set semsys:seminfo_semmns=11000
set semsys:seminfo_semmni=0x402
set semsys:seminfo_semmsl=4096
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set rlim_fd_max=8096
set rlim_fd_cur=1024
set noexec_user_stack=1
Edited by: [email protected] on Mar 6, 2009 12:25 PM

Shminfo_shmmax in /etc/system does not match project.max-shm-memory

If I specified 'shminfo_shmmax' in /etc/system and hava the system default in /etc/project(no change is made), the size of 'project.max-shm-memory' is 10 times larger than 'shminfo_shmmax'.
#more /etc/system // (16MB)
set shmsys:shminfo_shmmax=16000000
#prctl -n "project.max-shm-memory" -i project user.root
=> will display like below.
project: 1: user.root
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 1.49GB - deny -
system 16.0EB max deny
1.49GB is 10 times larger than 'SHMMAX'. If I add more entries /etc/system like below, max_shm_memory will become even larger.
#more /etc/system
set shmsys:shminfo_shmmax=16000000
set semsys:seminfo_semmni=2000
set shmsys:shminfo_shmmni=2000
set msgsys:msginfo_msgmni=2048
After I reboot with the above /etc/system and no change /etc/project(all default, no values added)
# prctl -n "project.max-shm-memory" -i project user.root
project: 1: user.root
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 29.8GB - deny -
system 16.0EB max deny -
Can anyone shed light about this area how to configure SHMAX in /etc/system right?

We saw similar behavior and opened a case with Sun.
The problem turns out to be that the (deprecated) /etc/system to (new) project resource limits isn't always one-to-one.
For example process.max-shm-memory gets set to shmsys:shminfo_shmmax * shmsys:shminfo_shmmni.
The logic here is that under the /etc/system tunings you might have wanted the maximum number of segments of the maximum size so the system has to be able to handle that. Make sense to some degree. I think Sun updated one of their info docs on the process at the end of our case to make this clearer.

Solaris 10 resource controls - /etc/system vs /etc/projects

Can someone please explain to me why, if we set the set the max shared memory segment in the /etc/system file using 'set shmsys:shminfo_shmmax=4294967296' we are seeing 800GB instead of 4GB when running 'prctl -n project.max-shm-memory':
/etc/system:
* Oracle 10.2.0 parameters
set shmsys:shminfo_shmmax = 4294967295
set shmsys:shminfo_shmmin = 1
set shmsys:shminfo_shmmni = 200
set shmsys:shminfo_shmseg = 20
set semsys:seminfo_semmni = 100
set semsys:seminfo_semmsl = 260
set semsys:seminfo_semmns = 1024
set semsys:seminfo_semopm = 100
set semsys:seminfo_semvmx = 32767
set rstchown = 0
* Setting in for Oracle 10 upgrade
set noexec_user_stack = 1
With /etc/system populated running prctl produces:
# /bin/prctl -n project.max-shm-memory -i process $$
process: 3428: sh
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 800GB - deny -
What is setting the maximum size for a shared segment to 800GB when using the /etc/system file to set the parameter?
If we remove the settings from /etc/system and use the normal default projects settings we get 1/4 of the physical memory, which is what we would expect to see.
Please note we will be using projects to control resources - I am just curious as to the effect of the /etc/system [set shmsys:shminfo_shmmax=4294967296] setting above

I have since found the answer - the 800GB is coming from shminfo_shmmax multiplied by shminfo_shmmni. This has been confirmed on another system with different values.

Metainit changing bootlist entry from ssd to scsa,00.bfcp in the /etc/system file

# metastat -p
d0 -m d1 d2 1
d1 1 1 c1t0d0s0
d2 1 1 c1t1d0s0
d10 -m d11 d12 1
d11 1 1 c1t0d0s1
d12 1 1 c1t1d0s1
d50 -m d51 d52 d53 1
d51 1 1 c1t0d0s4
d52 1 1 c1t1d0s4
d53 1 1 c1t2d0s4
# metainit -f d3 1 1 c1t2d0s0 ; metainit -f d13 1 1 c1t2d0s1 ;
d3: Concat/Stripe is setup
d13: Concat/Stripe is setup
# metastat -p
d0 -m d1 d2 1
d1 1 1 c1t0d0s0
d2 1 1 c1t1d0s0
d10 -m d11 d12 1
d11 1 1 c1t0d0s1
d12 1 1 c1t1d0s1
d50 -m d51 d52 d53 1
d51 1 1 c1t0d0s4
d52 1 1 c1t1d0s4
d53 1 1 c1t2d0s4
d3 1 1 c1t2d0s0
d13 1 1 c1t2d0s1
# metadb -i | grep dsk
a      m      p      luo      16      8192 /dev/dsk/c1t0d0s7
a           p      luo      8208      8192 /dev/dsk/c1t0d0s7
a           p      luo      16      8192 /dev/dsk/c1t1d0s7
a           p      luo      8208      8192 /dev/dsk/c1t1d0s7
# grep bootlist /etc/system
set md:mddb_bootlist1="ssd:23:16 ssd:23:8208 ssd:47:16 ssd:47:8208 ssd:39:16"
set md:mddb_bootlist2="ssd:39:8208"
# metadb -a -f -c 2 -l 8192 c1t2d0s7
# metadb -i | grep dsk
a      m      p     luo      16      8192 /dev/dsk/c1t0d0s7
a           p      luo      8208      8192 /dev/dsk/c1t0d0s7
a           p      luo      16      8192 /dev/dsk/c1t1d0s7
a           p      luo      8208      8192 /dev/dsk/c1t1d0s7
a           u           16      8192 /dev/dsk/c1t2d0s7
a           u           8208      8192 /dev/dsk/c1t2d0s7
# grep bootlist /etc/system
set md:mddb_bootlist1="scsa,00.bfcp:23:16 scsa,00.bfcp:23:8208"
set md:mddb_bootlist2="scsa,00.bfcp:47:16 scsa,00.bfcp:47:8208"
set md:mddb_bootlist3="scsa,00.bfcp:39:16 scsa,00.bfcp:39:8208"
# grep ssd /etc/path_to_inst
"/<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>/<a href="mailto:fp@0" target="_blank">fp@0</a>,0/<a href="mailto:ssd@w500000e010f2eee1" target="_blank">ssd@w500000e010f2eee1</a>,0" 0 "ssd"
"/<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>/<a href="mailto:fp@0" target="_blank">fp@0</a>,0/<a href="mailto:ssd@w500000e010f2f561" target="_blank">ssd@w500000e010f2f561</a>,0" 1 "ssd"
"/<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>/<a href="mailto:fp@0" target="_blank">fp@0</a>,0/<a href="mailto:ssd@w500000e010f32441" target="_blank">ssd@w500000e010f32441</a>,0" 2 "ssd"
"/<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>/<a href="mailto:fp@0" target="_blank">fp@0</a>,0/<a href="mailto:ssd@w500000e010f2f681" target="_blank">ssd@w500000e010f2f681</a>,0" 3 "ssd"
"/<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>/<a href="mailto:fp@0" target="_blank">fp@0</a>,0/<a href="mailto:ssd@w500000e010f32261" target="_blank">ssd@w500000e010f32261</a>,0" 4 "ssd"
"/<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>/<a href="mailto:fp@0" target="_blank">fp@0</a>,0/<a href="mailto:ssd@w500000e010f3d651" target="_blank">ssd@w500000e010f3d651</a>,0" 5 "ssd"
# grep scsa /etc/path_to_inst

You have specified the size of each replica with <i>-l 8192</i>, the default length is 8192 blocks. Have you tried running the metadb command without the length option included?

Installing VM SPARC 3.1.1 on T4-4 swith Solaris 5.10 update 11 (1/13) - not having /etc/system updated with values - is this a manual update?

Installing Oracle VM SPARC 3.1.1 on T4-4 swith Solaris 5.10 update 11 (1/13) - not having /etc/system updated with values - is this a manual update or is there required patch?
for /etc/system /etc/project for primary/control ldom and all guest ldoms, is there any patch that shold be installed to set memory settings when standing up guest-ldoms or the primary
/controller ldom? Running 8.6.0.b ILOM.
On another system finding shmsys, hires_tick, semsys and a few exclude settings in /etc/system file for ldoms on another T4-4 running 8.5.0.c ILOM.
Hopefully I've just missed a patch.
- JC

/etc/system is by default "empty" and contents only commented parameters or instructions.
And patches will not change this file. The shmsys, hires_tick, semsys and the other settings including /etc/project customizations that you have in the other machine was set manually or added during softwares configuration.

How to confirm changes to /etc/system on Solaris 9?

Hi: I added the following lines to the /etc/system and rebooted the machine.
set msgsys:msginfo_msgmnb=1073741824
set msgsys:msginfo_msgmax=65536
set msgsys:msginfo_msgtql=10000000
Anybody know a command on solaris 9 that will show these changes have taken into effect?
Thanks
Ravi

thanks.
ipcs -b does work
Hmm, can you see them with ipcs?
7/M.

Shmmax in /etc/system

Hi All,
we have a server of 8GB RAM , what can be maximum value I can assign for shmmax in /etc/system ..can i assign complete 8GB of RAM.
And what can be maximum sga_target that I can assign to a database in solaris..
In linux I know that to have a SGA of more than 2 Gb we assign hugepage memory.. In solaris what is the max limit for the SGA...
Please give me reply ASAP
Thanks in Advance...

you can set shmsys:shminfo_shmmax=8589934591
It has no effect other than allocating contiguous memory for a process. In your case since you are going to have 4 Dbs and you have 8 GB of physical memory, may be you can have SGA of each DB as 1.5 GB, but as Hans suggested earlier you should look at tuning manual to estimate, how much PGA your processes will take. Also you should take into account what will be going on in these 4 DBs i.e. how much activities will be there in these and allocate SGA accordingly. Allocating SGA of 1.5 GB to each without consideration to activities may not be good thing to do.

Could not mount USB drive on Solaris 10 x86 system

Hi All,
I am having difficulty mounting a USB drive on Solaris 10 x86 system with the following different unsuccessful attempts:
# uname -a
SunOS venus 5.10 Generic_139556-08 i86pc i386 i86pc
# rmformat
Looking for devices...
     1. Volmgt Node: /vol/dev/aliases/cdrom0
        Logical Node: /dev/rdsk/c0t0d0s2
        Physical Node: /pci@0,0/pci-ide@4/ide@0/sd@0,0
        Connected Device: TEAC     DV-28E-V         1.AC
        Device Type: DVD Reader
     2. Logical Node: /dev/rdsk/c4t0d0s2
        Physical Node: /pci@0,0/pci108e,534b@2,1/storage@9/disk@0,0
        Connected Device: WD       My Book 1140     1007
        Device Type: Removable
     3. Volmgt Node: /vol/dev/aliases/rmdisk0
        Logical Node: /dev/rdsk/c4t0d0p0
        Physical Node: /pci@0,0/pci108e,534b@2,1/storage@9/disk@0,0
        Connected Device: WD       My Book 1140     1007
        Device Type: Removable
# svcs volfs
STATE STIME    FMRI
online Apr_13   svc:/system/filesystem/volfs:default# ls -lt /mnt
total 0
# mount -F pcfs /dev/dsk/c4t0d0p0:c /mnt
mount: I/O error
# mount -F pcfs /dev/rdsk/c4t0d0p0:c /mnt
mount: Block device required
# mount -F pcfs /dev/dsk/c4t0d0s2:c /mnt
mount: I/O error
# mount -F pcfs /dev/rdsk/c4t0d0s2:c /mnt
mount: Block device required
# fsck /dev/dsk/c4t0d0p0
Can't open /dev/rdsk/c4t0d0p0: I/O error
# fsck /dev/rdsk/c4t0d0p0
Can't open /dev/rdsk/c4t0d0p0: I/O error
# fsck /dev/dsk/c4t0d0s2
Can't open /dev/rdsk/c4t0d0s2: I/O error
# fsck /dev/rdsk/c4t0d0s2
Can't open /dev/rdsk/c4t0d0s2: I/O errorSecond try,
# svcadm disable volfs
# svcs volfs
STATE          STIME    FMRI
disabled       20:47:00 svc:/system/filesystem/volfs:default
# mount -F pcfs /dev/dsk/c4t0d0p0:c /mnt
mount: I/O errorLast try,
# mkdir /rmdisk
mkdir: Failed to make directory "/rmdisk"; File exists
# ls -lt /rmdisk
total 4
lrwxrwxrwx   1 root     nobody        16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x   2 root     nobody       512 Sep 30 2009 unnamed_rmdisk
# cd /rmdisk
# ls -lt
total 4
lrwxrwxrwx   1 root     nobody        16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x   2 root     nobody       512 Sep 30 2009 unnamed_rmdisk
# ls -lt unnamed_rmdisk
total 0
# ls -lt rmdisk0
lrwxrwxrwx   1 root     nobody        16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
# df -h
Filesystem             size   used avail capacity Mounted on
/dev/dsk/c1t0d0s0      5.1G   4.0G   1.1G    78%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                   5.9G   984K   5.9G     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap2.so.1
                       5.1G   4.0G   1.1G    78%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd
swap                   5.9G   148K   5.9G     1%    /tmp
swap                   5.9G    32K   5.9G     1%    /var/run
/dev/dsk/c1t0d0s7      129G   1.7G   126G     2%    /export/home
# /etc/init.d/volmgt stop
# svcs volfs
STATE          STIME    FMRI
disabled       21:02:31 svc:/system/filesystem/volfs:default
# pwd
/rmdisk
# cd /
# ls -lt /rmdisk
total 4
lrwxrwxrwx   1 root     nobody        16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x   2 root     nobody       512 Sep 30 2009 unnamed_rmdisk
# /etc/init.d/volmgt st
# svcs volfs
STATE          STIME    FMRI
disabled       21:02:31 svc:/system/filesystem/volfs:default
# /etc/init.d/volmgt start
volume management starting.
# svcs volfs
STATE          STIME    FMRI
online         21:04:44 svc:/system/filesystem/volfs:default
# svcs volfs
# mount | grep rmdisk
# pwd
# ls -lt /rmdisk
total 4
lrwxrwxrwx   1 root     nobody        16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x   2 root     nobody       512 Sep 30 2009 unnamed_rmdisk
# ls -lt /rmdisk/unnamed_rmdisk
total 0
# iostat -En
c0t0d0           Soft Errors: 3 Hard Errors: 0 Transport Errors: 0
Vendor: TEAC     Product: DV-28E-V         Revision: 1.AC Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 3 Predictive Failure Analysis: 0
c1t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HUS1514SBSUN146G Revision: SA04 Serial No: 0921B2Y3PC
Size: 146.81GB <146810535936 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t1d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HUS1514SBSUN146G Revision: SA04 Serial No: 0921B2Z5NC
Size: 146.81GB <146810535936 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c4t0d0           Soft Errors: 21 Hard Errors: 0 Transport Errors: 0
Vendor: WD       Product: My Book 1140     Revision: 1007 Serial No:
Size: 2000.37GB <2000365289472 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 21 Predictive Failure Analysis: 0
#This is a working production system with 2 146.81GB mirrored hard disks. There is no disk error for either local or external 2TB Western Digital USB disks that works on Windows 7 or XP.
Any idea on what else to look for?
Thanks in advance,
Jack
Edited by: 797805 on 6/06/2012 04:48

Hi All,
Looks like it was a driver / incompatibility / unsupported issue since 2 other much smaller USB keys (Lexar USB Flash Drive – 32GB, SanDisk Cruzer Colors – 4GB) were successfully mounted automatically by volfs service as follows:
# df -h
Filesystem             size   used avail capacity Mounted on
/dev/dsk/c1t0d0s0      5.1G   4.0G   1.1G    78%    /
/dev/dsk/c1t0d0s7      129G   1.7G   126G     2%    /export/home
/vol/dev/dsk/c3t0d0/unnamed_rmdisk#1:c   3.7G   2.4G   1.3G    65%    /rmdisk/unnamed_rmdisk#1
/vol/dev/dsk/c2t0d0/unnamed_rmdisk:c    29G    96K    29G     1%    /rmdisk/unnamed_rmdiskIt also appears that the Device status of Not Ready from “iostat –En” below may not be correct either since both smaller drives are working fine:
# iostat -En
c4t0d0           Soft Errors: 23 Hard Errors: 0 Transport Errors: 0
Vendor: WD       Product: My Book 1140     Revision: 1007 Serial No:
Size: 2000.37GB <2000365289472 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 23 Predictive Failure Analysis: 0
c2t0d0           Soft Errors: 7 Hard Errors: 0 Transport Errors: 0
Vendor: Lexar    Product: USB Flash Drive Revision: 1100 Serial No:
Size: 31.41GB <31406948352 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 7 Predictive Failure Analysis: 0
c3t0d0           Soft Errors: 60 Hard Errors: 8 Transport Errors: 0
Vendor: SanDisk Product: Cruzer Colors+   Revision: 8.02 Serial No:
Size: 4.02GB <4022337024 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 8 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0In other word, the same question remains on whether it is possible to install a driver to overcome this issue and where to such driver?
It is necessary to install additional driver that came with the disk on Windows XP platform. However,
Thanks again,
Jack

Performance on Solaris 10 - Operating system paging

Has anyone experience performance issues after an upgrade from Solaris 9 to Solaris 10 on SAP systems with limited memory?
We have many systems that are on servers with 4 Gig of memory and ran well on Solaris 9. After an upgrade to Solaris 10 we are experiencing very high OS system paging rates. The response times of the SAP systems are very poor when this occurs. It seems to take very little load to cause this.
I realize more memory or decreases in Oracle or SAP memory parms will solve this but am wondering if there is anything on the Solaris OS that could resolve this?
Thanks,
Dan

DISM can be used but in global zone only (according to Sun document "Best Practive for Running Database in Solaris Containers" , the proc_lock_memory privilege which is required to run the ora_dism_ process is not available in non globale zone)
The doc i got is from 2005, so don't know if the Sun recommendations has been updated since then.
In order to activate DISM (if you are in a global zone), sga_max_size should be set up larger than the sum of sga components: db_cache_size, shared_pool_size ...)
Also look for the Sun Blueprint "Dynamic Reconfiguration and Oracle 9i Dynamic Resizable SGA" on http://www.sun.com/blueprints
If you use ISM because in a non-global zone, you can use oracle parameter lock_sga to ensure the SGA is loaded into the RAM and useism_for_pga = true to ensure PGA is loaded into the RAM.
Make sure you have enough RAM to hold filesystem cache (OS memory) , oracle memory, and applications memory
Make sur your PGA and SGA are correctly sized size, since you won't be able to dynamically change the ISM allocation. (see v$shared_pool_advice, v$db_cache_advice, v$pga_target_advice ...)
Take the usual precautions:
- have a successfull backup first
- do the change on a test machine
- and/or ask your vendor before proceeding
Other Doc to read ...
Note 697483 - "Oracle Dynamic SGA on Solaris" (recommends to read Sun doc n°230653)
Note 724713 - parameter settings for Solaris 10, here is an extract :
Only one parameter from SAP note 395438 should remain in file
etc/system
set rlim_fd_cur=8192
As described in SunSolve document 215536, the "Large Page Out Of the Box" (LPOOB) feature of the Solaris 10 memory management, first implemented in Solaris 10 1/06 (Update 1), can lead to performance problems when the system runs out of large chunks of free contiguous memory. This is because the Solaris 10 kernel by default will attempt to relocate memory pages to free up space for creating larger blocks of contiguous memory. Known symptoms are high %system CPU time in vmstat, high number of cross calls in mpstat, and Oracle calling mmap(2) to /dev/zero for getting more memory.
Memory page relocation for satisfying large page allocation requests can be disabled by setting the following Solaris kernel parameter in /etc/system
set pg_contig_disable=1
This will not switch off the LPOOB feature. Large memory pages will still be used when enough free space of contiguous memory is available, so the benefits of this feature will remain
Note 870652 - Installation of SAP in a Solaris Zone
Note 1246022 - Support for SAP applications in Solaris Zones
Edited by: Emmanuel TCHENG on Oct 13, 2009 12:02 PM

Audio driver fails to initialize when hires_tick=1 in /etc/system

Running Solaris 9 on Ultra 25 hardware. A customer's application requires hires_tick=1 be set in /etc/system. Once this change is made, audio does not work. Here is the error message from /var/adm/messages
Nov 1 12:34:11 <hostname> audiosup: [ID 384451 kern.warning] WARNING: audio15750: failure to power up the AC97 Codec
Nov 1 12:34:11 <hostname> audiosup: [ID 472426 kern.warning] WARNING: audio15750: attach() failure to init chip
There is a bug report on this: http://sunsolve.sun.com/search/document.do?assetkey=1-1-6567521-1
However, there does not appear to be a patch or other workaround aside from not setting hires_tick=1. That is not an option in this case.
Any thoughts?
Thanks,
Adam McManus

Running Solaris 9 on Ultra 25 hardware. A customer's application requires hires_tick=1 be set in /etc/system. Once this change is made, audio does not work. Here is the error message from /var/adm/messages
Nov 1 12:34:11 <hostname> audiosup: [ID 384451 kern.warning] WARNING: audio15750: failure to power up the AC97 Codec
Nov 1 12:34:11 <hostname> audiosup: [ID 472426 kern.warning] WARNING: audio15750: attach() failure to init chip
There is a bug report on this: http://sunsolve.sun.com/search/document.do?assetkey=1-1-6567521-1
However, there does not appear to be a patch or other workaround aside from not setting hires_tick=1. That is not an option in this case.
Any thoughts?
Thanks,
Adam McManus

Problem with /etc/system file

I changed /etc/system file and reboot Sun Solaris Intel (5.8)
and I got :
* IPC Semaphores module is not loaded
I did same thing on another box before and was fine. I now that I run some utility before rebooting, but I forget which one.
Can somebody help me.

Thank you very much.
That solve my problem. The problem, if I undersend well, was not in my new /etc/system file, problem was (it is not problem) because I run sysdef right after booting machine and that modul probably is not loaded yet. With forceload sysdef shows what I expected. About
some utility, probably that was something else.
Regards,
Ivan Aksentijevic

/etc/system got corrupted

Dear All,
if on a running server /etc/system file got corrupted, then what will happen...means the server will continue running or it will come down to OK prompt.....

Check if your OS volumes are mirrored ( # df -k ) if root ( / ) is /dev/md/dsk/d0 then you will need to add the metaroot entry back.
Mine looks like this, you can re-create it by re-running mataroot
* Begin MDD root info (do not edit)
forceload: misc/md_trans
forceload: misc/md_raid
forceload: misc/md_hotspares
forceload: misc/md_sp
forceload: misc/md_stripe
forceload: misc/md_mirror
forceload: drv/pcisch
forceload: drv/qlc
forceload: drv/fp
forceload: drv/ssd
rootdev:/pseudo/md@0:0,0,blk
* End MDD root info (do not edit)
* Begin MDD database info (do not edit)
set md:mddb_bootlist1="ssd:7:16 ssd:7:1050 ssd:7:2084 ssd:15:16 ssd:15:1050"
set md:mddb_bootlist2="ssd:15:2084"
* End MDD database info (do not edit)

/etc/system file

How do I set a limit for a per process data size in the /etc/system file?
Thank you.
coscop

Coscop,
You can't. The only limit you could set via /etc/system is
file descriptor limits (rlim_fd_cur & rlim_fd_max). ie.:
set rlim_fd_max = 4096
The rest, including the process heap segment, needs
to be set via shell (like in the .profile). Later version of
Solaris has the plimit command which allows to set the limit
on the running PID. Solaris Resource Manager was developed
around the Solaris 8 release time frame, I don't believe
it has a way to limit the heap segment per prccess either.
Hope this helps.
hae

Solaris 10:unable to mount a solaris root file system

Hi All,
I am trying to install Solaris 10 X86 on a Proliant DL385 Server it has a Smart array 6i, I have download the driver from the HP web site, on booting up the installation CD 1, adding the device driver, it sees the device but now says it can��t mount the device. Any clues what I need to do?
Screen Output:
Unable to mount a Solaris root file system from the device
DISK: Target 0, Bios primary drive - device 0x80
on Smart Array 6i Controller on Board PCI bus 2, at Dev 4
Error message from mount::
/pci@0,0/pci1022,7450@7/pcie11,4091@4/cmdk@0,0:a: can't open - no vtoc
any assistence would be appreciated.

Hi,
I read the Message 591 (Agu 2003) and the problem is quite the same. A brief description: I have aLaptop ASUS with HDD1 60GB and a USB storage HDD (in next HDD2) 100GB. I installed Solaris 10 x86 on HDD2 (partition c2t0d0s0). At the end of installation I removed the DVD and using BIOS features I switched the boot to HDD2. All ok; I received the SUN Blue Screen and I choose the active Solaris option; but at the beginning of the boot I received the following error message
Screen Output:
Unable to mount a Solaris root file system from the device
DISK: Target 0: IC25N060 ATMR04-0 on Board ....
Error message from mount::
/pci@0,0/pci-ide2,5/ide@1/cmdk@0,0:a: can't open
any assistence would be appreciated.
Regards

Sd/ssd max throttle in solaris 10 etc/system

Similar Messages

Maybe you are looking for