01-01-2020
Quote:
Originally Posted by
cokedude
I only set nofiles = 64000. Do you think that is to high? I was just using the above as an example.
64k is fine - its very unlikely that oracle will have this many files open at the same time anyways (which is what this tunable determines) as the Database itself is in just a number of large .dbf files. In addition they will have some text files and libraries open - but I doubt the user oracle even owns 64.000 files
10 More Discussions You Might Find Interesting
1. AIX
Hi,
I have a query that suppose the first or last name of the user changes and we need to change its userid for aix too. Then in that case how do we handle this scenario??I guess we can't change the user id so we should re-create the new id and associate all the data of the old id. But I donno... (1 Reply)
Discussion started by: tintin@10
1 Replies
2. UNIX for Dummies Questions & Answers
ulimit -a gives the following output:$ulimit -a
time(seconds) unlimited
file(blocks) 2097152
data(kbytes) 131072
stack(kbytes) 16384
memory(kbytes) unlimited
coredump(blocks) 32768
nofiles(descriptors) 400
vmemory(kbytes) 147456
Abot output... (3 Replies)
Discussion started by: nervous
3 Replies
3. AIX
how to set the ulimit on AIX 5.2 version? (3 Replies)
Discussion started by: Shilpi
3 Replies
4. AIX
Hi Guys,
How do I increase the filesize ulimit for user jf01474, using the same value as of user oracle?
Ex: /etc/security/limits
default:
fsize = 4194302
core = 2097151
cpu = -1
data = 262144
rss = 65536
stack = 65536
... (3 Replies)
Discussion started by: sky_lark02
3 Replies
5. HP-UX
Hi,
on HP-UX when I run command
ulimit -a
I get
time(seconds) 4096
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) 8192
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 4096
Now I want to change
file(blocks) ... (2 Replies)
Discussion started by: namita.mundada
2 Replies
6. UNIX for Dummies Questions & Answers
Hello AIX gurus,
I have a requirement where I have to change user ID of user "myuser" from 100 to 200 and also the group ID of "mygroup" from 2 to 3. Please note that "myuser" has "mygroup" as it's primary group.
What steps do I need to follow for this and in what order? Also can you please... (2 Replies)
Discussion started by: sacguy08
2 Replies
7. AIX
Hello,
How can I setup the ulimit for memory permanent
ulimit -m unlimited
ulimit -a Output from the ulimit command should be similar to the following:time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 2097152
stack(kbytes) 32768... (4 Replies)
Discussion started by: filosophizer
4 Replies
8. UNIX for Dummies Questions & Answers
Hello All,
If a user in AIX is locked due to multiple failed login attempts. How do I find out the IP address from where failed attempts were made?
regards,
Roshni (0 Replies)
Discussion started by: RoshniMehta
0 Replies
9. Red Hat
The root user runs the following
ulimit -a | grep open
and gets a result of
open files (-n) 8162
A user runs the same command and gets a result of
open files (-n) 2500
How can you set the ulimit of the user to... (2 Replies)
Discussion started by: jsanders
2 Replies
10. AIX
Hi,
what are the ideal/best/recommended ulimit settings for a root user in AIX?
I understand that it depends on our environment. But I would like to know...what are settings you guys use in your environment for best performance.
default:
fsize = 2097151
core = 2097151
... (8 Replies)
Discussion started by: System Admin 77
8 Replies
LEARN ABOUT HPUX
maxfiles_lim
maxfiles_lim(5) File Formats Manual maxfiles_lim(5)
NAME
maxfiles_lim - hard maximum number of file descriptors per process
VALUES
Failsafe
Default
Allowed values
The minimum value allowed is 32. The maximum value allowed is 1048576, or 1M. The value is further constrained in that it must be equal
or greater than the soft limit,
Specify a positive integer value.
Recommended values
At runtime, a warning will be issued if the tunable is set to a value greater than 409600, or 400K. This is beyond the tested limit.
At runtime, a warning will be issued if the value is not a multiple of the file descriptor chunk (multiple of 8) size. This is not a seri-
ous warning, just an information message for the administrator.
DESCRIPTION
specifies the system hard limit for the number of file descriptors that a process is allowed to have for open files at any given time. It
is possible for a nonsuperuser process to increase its soft limit up to this hard limit.
Who Is Expected to Change This Tunable?
Anyone expecting to run applications using large numbers of file descriptors.
Restrictions on Changing
The tunable is dynamic (tuning will take effect immediately on the running system).
Dynamic changes affect all existing processes in the system except:
o Processes that have more file descriptors allocated than allowed by the new limit,
o Processes that have specifically set their limits through a call to or
When Should the Value of This Tunable Be Raised?
The tunable should be increased when large numbers of file descriptors are expected to be open by several processes.
What are the Side Effects of Raising the Value?
There is no immediate effect of raising the value of However, doing so allows any process to allocate more file descriptors, potentially
consuming more system memory.
When Should the Value of This Tunable Be Lowered?
The value should be lowered to limit the number of open file descriptors per process on a system and reduce system memory consumption.
What are the Side Effects of Lowering the Value?
Lowering the value of bounds memory consumption due to file descriptors for processes that are not already over the new limit.
What Other Tunable Values Should Be Changed at the Same Time?
The value assigned to must be less than or equal to the value of
Kernel checks during tunable setting ensure these restrictions.
WARNINGS
For values greater than 65535, compatibility for the obsolescent will be affected. For correct operation, all applications must use
instead of If the system still has applications using setting to 65535 or less will maintain compatibility, unless the process being
queried has used to change its maximum limit of open files to a value greater than 65535.
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
kctune(1M), sam(1M), setrlimit(2), gettune(2), settune(2), pstat(2), ulimit(2), maxfiles(5).
Tunable Kernel Parameters maxfiles_lim(5)