SBS server does not startup in a backup group
Last updated on OCTOBER 18, 2016
Applies to:Oracle MessageQ - Version 5.0 and later
HP OpenVMS Alpha
The goal is to start SBS server in the backup group of a Automatic synchronized hot cluster failover setup.
A backup group running on a non-primary member of a cluster is disconnected from the message bus by not starting the link drivers, and is also prevented from accessing cluster common queue files (SAF, DQF, PCJ) by not starting the MRS server. Client library servers and journal servers are likewise not started. Nevertheless, the messaging services of the local group, provided by the COM server itself, and the SBS server are required in order for the failover group and its applications to startup and be ready for the hot-failover which takes place as the previous primary group fails, and the cluster lock is obtained by the failover group.
However, the Selective Broadcasting Server is inhibited from starting. This means that applications which normally are able to register with availablity services on non-cluster hot-failover backup groups are no longer able to do so because they are in a cluster.
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