My Oracle Support Banner

EM13c : Master Agent Switch Happening To Node That Monitors DB Instance Which Is Unhealthy (Doc ID 2715834.1)

Last updated on SEPTEMBER 30, 2020

Applies to:

Enterprise Manager Base Platform - Version 13.2.0.0.0 to 13.4.0.0.0 [Release 13c]
Information in this document applies to any platform.

Symptoms

In Enterprise Manager (EM) Cloud Control, Master Agent switch can happen in the below two scenarios:

1. Agent clean heartbeat post the blackout end:
# When the Agent (A1) comes out of the blackout, It sends the clean heartbeat to OMS.
# As a part of recording the heartbeat flow, there is a validation on the status of the Current Master Agent(A2).
# If the Master Agent status (A2) is not UP and the current agent (A1) status is UP, this would again trigger the Master Agent switch to A1 without
explicitly checking the DB instance status monitored by A1.

2. DB instance Status change:
# When the instance(DB1) status change is received and new status is UP, there is validation to check if the current Master agent(A2)'s instance(DB2) is UP.
# There is no explicit validation in place to check the status of the agents A1 and A2.

Cause

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
Symptoms
Cause
Solution
References


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