Solaris Cluster 3.x Resource Fails To Start Due To Error "Could not setup scheduling parameters: Permission denied"
Last updated on JANUARY 15, 2018
Applies to:Solaris Cluster - Version 3.2 U2 to 3.3 U1 [Release 3.2 to 3.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
A resource group called app1-rg failing to start.
Global zone messages we see all methods successfully start and then
Notice that the Permission denied was not reported the second time.
(if the Resource Group and Resources are all in the global zone then you will see everything in the global zone messages)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms