01-01-2020
Greetings and Happy New Year!
You can't judge like that what is good/bad...
Oracle is no ordinary user: many users access to files using oracle UID the same for processes etc
So it will depend on the size of your RDBMS or how many instances you have running on a server, how many processes are "oracle" etc the same for files and file size: no ordinary user would produce a file on a system the size of a full export (oracle)...
Why unlimited as value is not a good idea unless you know what you are doing AND what the others do:
Just an example: if a coder badly checked his new code that went in production ( or just a bug...) fall on a case you case have files opening but not closed correctly, worse though quite funny when it occurs: executing an infinite loop opening new processes...
You end with a freeze of the system where if lucky and an admin can connect will shutdown gracefully the box, more severe no one can connect and you have no other choice but to power off...
AIX at least lets you define on a specific user basis, may not be the case of all Unixes you see
Addendum:
Q: Do you have any issues? Giving a lot of resources will give you peace ( no errors or warning of running out of resources...) only that waste of resource will affect performance, if that is OK with you and production are happy, well why worry except for the case you do have an issue, it will be in proportion with what you gave
Last edited by vbe; 01-01-2020 at 05:29 AM..
Reason: Typos and addendum
This User Gave Thanks to vbe For This Post:
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
ulimit(1) General Commands Manual ulimit(1)
NAME
ulimit - Sets or reports a resource limit
SYNOPSIS
ulimit [-HSacdfmnstvw] [limit]
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
ulimit: XCU5.0, XBD5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
[Tru64 UNIX] The limits specified for the resources are hard limits. A hard limit cannot be increased once it is set. [Tru64 UNIX]
The limits specified for the resources are soft limits. A soft limit can be increased up to the value of the hard limit. [Tru64 UNIX]
Lists all of the current resource limits. The limit operand is not permitted with this option. [Tru64 UNIX] The limit operand specifies
the number of 512-byte blocks for core dumps. [Tru64 UNIX] The limit operand specifies the number of Kilobytes for the data area. The
limit operand specifies the number of 512-byte blocks for files written by child processes (files of any size can be read). [Tru64 UNIX]
The limit operand specifies the number of Kilobytes for the size of physical memory. [Tru64 UNIX] The limit operand specifies the number
of file descriptors. [Tru64 UNIX] The limit operand specifies the number of Kilobytes for the stack area. [Tru64 UNIX] The limit op-
erand specifies the number of seconds to be used by each process. [Tru64 UNIX] The limit operand specifies the number of Kilobytes for
virtual memory. This option is supported only if RLIMIT_VMEM has been defined in /usr/include/sys/resource.h at compile-time. [Tru64
UNIX] The limit operand specifies the number of Kilobytes for the swap area. This option is supported only if RLIMIT_SWAP has been
defined in /usr/include/sys/resource.h at compile-time.
OPERANDS
If no options are specified, this is the number of 512 byte blocks to use as the new limit to file size. Otherwise, it is the limit applied
to the resource indicatd by the option.
[Tru64 UNIX] This operand is not allowed with the -a option.
If this operand is omitted, the current limit for the indicated resource is reported.
DESCRIPTION
This command sets, or reports, the limit on the size of system resources, as indicated by the option.
[Tru64 UNIX] If neither the -H option nor the -S option is specified, the limit applies to both hard and soft limits. If only the -a
option is specified, soft limits are reported.
If there is no limit on a resource, the limit is reported as unlimited.
NOTES
The ulimit command affects only the current execution environment, therefore it has no effect when run in a separate execution environment
such as one of the following:
nohup ulimit -f 10000 env ulimit 10000
RESTRICTIONS
Once a limit has been decreased, only a user with superuser privileges may increase it, even back to its original value.
EXIT STATUS
The following exit values are returned: Successful completion. A request for a higher limit was rejected or an error occurred.
EXAMPLES
To set the file size limit to 51,200 bytes, enter: ulimit -f 100 To report the current file size limit, enter: ulimit The following example
displays all current resource limits: % ulimit -a
time(seconds) unlimited file(blocks) unlimited data(kbytes) 131072 stack(kbytes) 2048 memory(kbytes)
84280 coredump(blocks) unlimited nofiles(descriptors) 4096 vmemory(kbytes) 1048576
ENVIRONMENT VARIABLES
The following environment variables affect the execution of ulimit: Provides a default value for the internationalization variables that
are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization
variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string
value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of
bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the
format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of
LC_MESSAGES.
SEE ALSO
Routines: ulimit(3)
Standards: standards(5)
ulimit(1)