- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Autosys and limits.conf recognition of Oracle User...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2015 10:11 AM
08-26-2015 10:11 AM
Autosys and limits.conf recognition of Oracle User Job
We're using Autosys R11 as the Job Control And Scheduler.
There is an Oracle Script that starts a Database Instance.
The Oracle user has environmental linits in /etc/security/limits.conf i.e.:
oracle soft memlock 65011712
oracle hard memlock 65011712
The above settings are important for proper startup of Oracle. When the Oracle user (lamanually logged in as oracle) runs the script, it works fine.
When Autosys runs the script with oracle as the effective user as well as settings to source oracle's profile, it does not work because the above oracle limits.conf settings does not seem to be recognized by the execution environment.
I know the fix is real easy and that is to add "ulimit" lines to autosys' or the oracle user's profile settings but I thought Linux should always recognize what is set in limits.conf as long as the effective uid/gid of the executing script is set to what is listed -- in this case oracle.
Any ideas why Autosys executed scripts do not seem to honour limits.conf settings?