OBIEE 12c: The 'start.sh' Script Fails To Start The Primary Node In A Horizontal Cluster Environment When Other Nodes Are Down (Doc ID 2109336.1)

Last updated on JUNE 05, 2016

Applies to:

Business Intelligence Server Enterprise Edition - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

You have configured a horizontally scaled-out environment with node1 (primary) and node 2 (secondary).

You can start both start the node manager on node 2 and then start all components by running the [DOMAIN_HOME]/bitools/bin/start.sh script from node 1 (primary). This all works well.

Note: On a related topic, you always run the start.sh script from the node where the AdminServer is running.  The AdminServer should be configured for failover to other nodes in case you need to run start.sh from node 2,3,4,n.

 

 

Consider the following scenario when you stop all components on node 2,3,n and then run 'start.sh' on Node 1.



Cause

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