Solaris Cluster 3.x and Oracle Communications Network Charging and Control: Why Do Some Resource Groups Not Run on Their Preferred Node ?
Last updated on SEPTEMBER 06, 2016
Applies to:Solaris Cluster - Version 3.2U1 4/08 to OSC 3.3 3/13 [Release 3.2 to 3.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)
This article explains why some Solaris Cluster RGs (Resource Group) that the OCNCC (Oracle Communications Network Charging and Control) application use may not be running on their preferred node in or after certain unusual situations.
It allows the System Administrator to identify if and where a manual intervention is necessary to recover to a normal Cluster state, should it be different to the initial startup state.
It focuses on the OCNCC Clustered SMS (Service Management Server) implementation.
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