Solaris Cluster 3.x with Cluster Volume Manager: Oracle Database Goes Down and grep "returned error (127)" is Reported When Executes scal_dg_probe to Check Disk Group
Last updated on MARCH 06, 2017
Applies to:Solaris Operating System - Version 10 9/10 U9 and later
Oracle Communications Network Charging and Control - Version 2.4.0 to 3.2.0 [Release 2.4 to 3.2.0]
Solaris Cluster - Version 3.1 to 3.3 U2 [Release 3.1 to 3.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
When this problem happens, the following symptoms may be witnessed
- The database resource group for one of cluster nodes has been moved to "Pending online blocked No"
- Attempts to establish SQL sessions fail with the error message "Oracle is not available" reported.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms