OBIEE 11g: Scale Out Fails During Configuration On A Machine With Multiple NICs

(Doc ID 2112316.1)

Last updated on MARCH 16, 2016

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.9.0 and later
Information in this document applies to any platform.
Workaround is to use a script to change the IP address.

Symptoms

The installer hangs at the configuration phase (Configuration Assistant) when attempting to scale-out an OBIEE environment on another node.
The "Starting Scaled Out Manager Server" step hangs and it does not complete:

 

 

The following error appears in the installation log:

Caused by: javax.management.OperationsException: WARNING: Element Type: MANAGED_SERVER
Element Id: bi_server2
Operation Result: FAILED_CONTACTING_MANAGED_SERVERS
Detail Message: Specified BI Managed Servers are shut down: bi_server2.
at oracle.bi.management.adminservices.mbeans.impl.BIDomainMBeanImpl.throwExceptionIfEventLogOverThreshold(BIDomainMBeanImpl.java:284)
at oracle.bi.management.adminservices.mbeans.impl.BIDomainMBeanImpl.commit(BIDomainMBeanImpl.java:242)
at oracle.bi.management.adminservices.mbeans.impl.BIDomainMBeanImpl.commit(BIDomainMBeanImpl.java:251)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 

Environment Information:

 

Changes

 Scale-out to Exalogic nodes that have multiple network cards and bi_server2 is picking up a private card as its Default channel when its started (per scale out process).

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