Oracle SuperCluster OAM Coherence Cluster Startup Failures Due To Coherence Errors
(Doc ID 2342628.1)
Last updated on MAY 06, 2022
Applies to:Oracle Coherence - Version 220.127.116.11 and later
Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
This is an issue in the Oracle Access Manager cluster with two oam-managed servers running on different Supercluster hosts. Adminserver and oamserver1 resides on one node while oamserver2 on another node, cluster communication is unicast with PreferIPv4 is set on both machines. On the first startup both OAM instances come up ok but at later stages while rebooting one of the oamserver failed to join the cluster.
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