Re: solaris 10 kernel parameters
- From: Adric Norris <spikey.mcmarbles@xxxxxxxxx>
- To: joe_dba@xxxxxxxxxxx
- Date: Thu, 8 Oct 2009 09:55:05 -0500
On Wed, Oct 7, 2009 at 20:51, Joe Smith <joe_dba@xxxxxxxxxxx> wrote:
> What do most people do:
>
> Keep using /etc/system in Solaris 10 or the Resouce Control Facility? Or
> do people ignore the parameters and not set any in /etc/system or
> the Resouce Control?
>
We're using the resource control facility (/etc/project) almost exclusively
for our Solaris 10 boxes. I say *almost* because the
*noexec_user_stack*setting still has to go into /etc/system. Here's
an example of our typical
project setup (which must be run as root) for new database server.
projadd -U oracle -c "Oracle database settings" \
-K "process.max-file-descriptor=(privileged,65536,deny)" \
-K "process.max-sem-nsems=(privileged,512,deny)" \
-K "process.max-stack-size=(privileged,16777216,deny)" \
-K "project.max-sem-ids=(privileged,512,deny)" \
-K "project.max-shm-ids=(privileged,512,deny)" \
-K "project.max-shm-memory=(privileged,32GB,deny)" \
user.oracle
One caveat we discovered is that the 10.2.0.3 version of CRS doesn't
(always?) initialize the project settings when transitioning from root to
oracle, so you get different resource limits depending upon how the database
was started. This is fixed in the 11.1.0.x release, which we had to upgrade
to anyway in order to obtain various stability bugfixes.
--
"I'm too sexy for my code." - Awk Sed Fred.
Other related posts:
