OBIEE 11g: Error: "<BEA-000133> <Waiting to synchronize with other running members of bi_cluster.>" after Enabling Https Listen Port on Bi_server1 (Doc ID 1332151.1)

Last updated on JANUARY 23, 2017

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.5.0 [1308] and later
Business Intelligence Suite Enterprise Edition - Version 11.1.1.5.0 [1308] and later
Information in this document applies to any platform.
Checked for relevance on 13-May-2013

Symptoms

You have enabled SSL for OBIEE 11g. When you restart bi_server1, you get the following error:

<Jun 17, 2011 8:47:16 AM BST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of bi_cluster.>
<Jun 17, 2011 8:47:46 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jun 17, 2011 8:47:46 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Jun 17, 2011 8:47:46 AM BST> <Error> <Cluster> <BEA-003111> <No channel exists for replication calls for cluster bi_cluster>
<Jun 17, 2011 8:47:46 AM BST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: No replication server channel for bi_server1
java.lang.AssertionError: No replication server channel for bi_server1
at weblogic.cluster.replication.ReplicationManagerServerRef.initialize(ReplicationManagerServerRef.java:120)
at weblogic.cluster.replication.ReplicationManagerServerRef.<clinit>(ReplicationManagerServerRef.java:83)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at weblogic.rmi.internal.BasicRuntimeDescriptor.getServerReferenceClass(BasicRuntimeDescriptor.java:469)
Truncated. see log file for complete stacktrace
>
<Jun 17, 2011 8:47:47 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 17, 2011 8:47:47 AM BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 17, 2011 8:47:47 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>


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