After New Install Getting Oracle Coherence GE 3.7.1.12 Error and BEA-002606 Error (Doc ID 2160475.1)

Last updated on APRIL 03, 2023

Applies to:

Symptoms

On :  2.15.1 version, Installation

Oracle Coherence GE 3.7.1.12  

Getting Coherence error on the new 2.15.1 PRODDEF environment on Exalogic server.

ERROR
-----------------------
2016-07-11 12:56:48,548 [ Logger@1233980685 3.7.1.12 ] ERROR Coherence - 2016-07-11 12:56:48.548/40.110 Oracle Coherence GE 3.7.1.12 (thread=Cluster, member=n/a): This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. This member specified a cluster name of "ohicfg2_cluster" which did not match the name of the running cluster. This indicates that there are multiple clusters on this network attempting to use overlapping network configurations. Rejected by Member(Id=1, Timestamp=2016-07-11 10:37:29.012, Address=155.nn.nn.n:8406, MachineId=31942, Location=site:,machine:lxappd001a,process:59203,member:ohipqa2_managed_server1, Role=WeblogicServer).
2016-07-11 12:56:48,553 [ Logger@1233980685 3.7.1.12 ] ERROR Coherence - 2016-07-11 12:56:48.553/40.115 Oracle Coherence GE 3.7.1.12 (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install new environment.
2. Deploy 2.15.1.0.0 proddef.
3. Start.
4. Receive error given above.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.