My Oracle Support Banner

OMS GC Domain defaultCoherenceCluster Startup Refresh Missing the Targets In the EM Console Post Patching. (Doc ID 2851115.1)

Last updated on FEBRUARY 28, 2024

Applies to:

Enterprise Manager for Fusion Middleware - Version and later
Oracle Coherence - Version and later
Information in this document applies to any platform.


User reported that defaultCoherenceCluster startup refresh failure intermittently in OMS EM environment post patching. Looking within the OEM console, it showed the status of pending state.

Targets => Middleware
... the defaultCoherenceCluster target was a single entry (did NOT have any sub-targets)

Therefore user went through the screens and ran Add/Upgrade targets and user successfully added N targets. Then user sees a bunch of sub-targets under defaultCoherenceCluster.

Targets => Middleware
... the defaultCoherenceCluster target now shows sub-targets and all targets are UP (cache instances as sub-targets)

Can you explain the purpose of the defaultCoherenceCluster, what processes within OEM that rely on those targets and what happens if the coherence sub-targets are not created?


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

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