How To Make ulimit Settings Persistent across Server Reboot to Prevent ORA-4030 errors
(Doc ID 603660.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 10.2.0.4 [Release 9.2 to 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Information in this document applies to any platform.
Goal
UNIX operating systems have the ability to limit the amount of various system resources available to a user process. These limitations include how many files a process can have open, how large of a file the user can create, and how much memory can be used by the different components of the process such as the stack, data and text segments.
Ulimit is the command used to accomplish this. Undersized values for such resources can lead to ORA-04030 errors.
The goal of this document is:
After making the changes to ulimit values, how to make these changes persistent across server reboot for oracle user.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |