Also ensure these lines exist for memlock (often required together):
The error occurs when the operating system . Common reasons:
In many enterprise environments, SELinux is set to 'Enforcing' mode. This can prevent the clusterware from modifying its own execution priority. You can temporarily set SELinux to 'Permissive' to see if the error disappears: setenforce 0
Then create custom policy.
Check the current limits for the 'grid' user (or whichever user owns the Grid Infrastructure installation). Run the following command as the grid user:
-1 removes the limit entirely. For production, 1000000 is safer.
Also ensure these lines exist for memlock (often required together):
The error occurs when the operating system . Common reasons:
In many enterprise environments, SELinux is set to 'Enforcing' mode. This can prevent the clusterware from modifying its own execution priority. You can temporarily set SELinux to 'Permissive' to see if the error disappears: setenforce 0
Then create custom policy.
Check the current limits for the 'grid' user (or whichever user owns the Grid Infrastructure installation). Run the following command as the grid user:
-1 removes the limit entirely. For production, 1000000 is safer.
