SOA Fails to Join Coherence Cluster During the First Start After Upgrade

After you upgrade Oracle Identity Manager (OIM) and Oracle Access Manager (OAM) integrated environment, when you start the Oracle SOA Suite Server for the first time, the coherence cluster fails to start with the following error:

<Error> <com.oracle.coherence> <BEA-000000>  <2017-08-03 15:49:14.010/123.585 Oracle Coherence GE 12.2.1.3.0 
<Error>  (thread=Cluster, member=n/a): This member could not join the cluster because  of a mismatch 
between Coherence license types. This member was attempting to  run in dev mode. 
Rejected by Member(Id=1, Timestamp=2017-08-03 15:36:20.874,  Address=10.241.57.43:57023, MachineId=8125,  
Location=process:19490,member:oam_policy_mgr1, Role=WeblogicServer).>  
<Aug 3, 2017 3:49:14,017 PM UTC> <Error> <com.oracle.coherence> <BEA-000000>  
<2017-08-03 15:49:14.017/123.592 Oracle Coherence GE 12.2.1.3.0 <Error>  (thread=[ACTIVE] ExecuteThread: 
'10' 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)        
at  com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Serv  ice.CDB:38) 

This occurs if both the OIM and OAM WebLogic domains have the same default coherence cluster port. To resolve this issue, change the cluster port for either OAM or OIM by doing the following, pre-upgrade:

1. Log in to the WebLogic Administration console using following URL:
   http://weblogic_admin_host:weblogic_admin_port/console
2. Click Environments on the left navigation pane.
3. Click Coherence Clusters, and then click defaultCoherenceCluster.
4. Change the port from 7574 to 7575 for either OIM or OAM .