*** How to change Hard Limit / Open file descriptors LIVE in Solaris 10
underh20
Our server is running Solaris 10. We are in the processing of
upgrading to Oracle 11G. An issue has come up regarding the hard
limit (see below). The server has hard limit set to 65535
and Oracle needs 65536. Is there any way, i.e., without reboot of
server, to increase this
value for the Oracle user during installation ?
=======================================================
Oracle installer is looking at Hard Limit:Open file descriptors
Expected Value:65536
Actual Value:65535
=======================================================
Thanks,
Bill
hume.sp...@bofh.ca
> Our server is running Solaris 10. We are in the processing of
> upgrading to Oracle 11G. An issue has come up regarding the hard
> limit (see below). The server has hard limit set to 65535
> and Oracle needs 65536. Is there any way, i.e., without reboot of
> server, to increase this
> value for the Oracle user during installation ?
First, check to see whether any of your login scripts are setting a limit.
A simple "unlimit descriptors" at the shell prompt on my machine (I use
tcsh) raises my descriptor limit to 65536.
Otherwise, try using /etc/project to raise the ou'll want to employ /etc/project and raise the value for your oracle
user. It's just like raising the max-shm-memory limit:
% grep oracle /etc/project
user.oracle:100:Oracle 11g:::process.max-file-descriptor=(privileged,128000,deny)
You'll have to log out and back in to get the new limit.
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
Frank Langelage
I installed 11gR2 some time ago on my Solaris 10 workstation.
It complained that a prerequisite was not fulfilled, I can't remember
what it was exactly.
But I could ignore this warning and do the installation.
The difference of this 1 file descriptor can safely be ignored in my
opinion.
underh20
script. We are not using /etc/project
in general. However, we do notice that the following value exist in /
etc/system :
set rlim_fd_max = 65535
Could this be change to 65536 without reboot? We tried to issue the
following command at the oracle
user's shell prompt but to no avail.
$ ulimit -n 65536
/bin/ksh:ulimit: exceeds allowable limit
Any idea,
Thanks,
Bill
On Feb 3, 10:38 am, hume.spamfil...@bofh.ca wrote:
Stefan Krueger
> Currently, no "ulimit descriptors" value is set at the user login
> script. We are not using /etc/project
> in general. However, we do notice that the following value exist in /
> etc/system :
>
> set rlim_fd_max = 65535
>
> Could this be change to 65536 without reboot? We tried to issue the
> following command at the oracle
> user's shell prompt but to no avail.
>
> $ ulimit -n 65536
> /bin/ksh:ulimit: exceeds allowable limit
>
> Any idea,
>
> Thanks,
>
> Bill
you could try setting this value with mdb, i.e.
mdb -kw
and then
rlim_fd_max/W 0t65536
check with
rlim_fd_max/D
hope this helps
Casper H.S. Dik
>you could try setting this value with mdb, i.e.
>mdb -kw
>and then
>rlim_fd_max/W 0t65536
>check with
>rlim_fd_max/D
>hope this helps
And use "plimit" on running processes.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
peter....@gmail.com
http://docs.oracle.com/cd/E19455-01/806-6779/chapter2-32/index.html
hume.sp...@bofh.ca
11? After all, the post you've responded to is FOUR YEARS OLD, and is
referring to Solaris 10.
Casper H.S. Dik
>peter....@gmail.com wrote:
>> nope, mdb will not work for rlim_fd_max :D
>What? Yes it would, I've done it. Although maybe that's changed in Solaris
>11? After all, the post you've responded to is FOUR YEARS OLD, and is
>referring to Solaris 10.
by the kernel such as init(1m) but not during fork(); so you can set it
using mdb but it has only effect before init is started.
Casper