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 MARCH 25, 2019
Applies to:Business Intelligence Server Enterprise Edition - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
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.
Consider the following scenario when you stop all components on node 2,3,n and then run 'start.sh' on Node 1.
- None of the components on node 2,3,n start (which is normal) because the nodemanager cannot be contacted.
- None of the components on node 1 start which is the problem.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document