EM 12c, 13c: Scan Listener Target Not Moving To New Agent After Relocation

(Doc ID 2281218.1)

Last updated on JUNE 27, 2017

Applies to:

Enterprise Manager for Oracle Database - Version 12.1.0.5.0 and later
Information in this document applies to any platform.

Symptoms

After a Scan Listener is failed over or relocated to another node, EM Cloud control shows this target as down.
Investigating further shows that the 'Scan Listener' target is still being monitored by previous node's agent and not being monitored by new node's agent.

Agent log shows following entries:

So the proxy did not start on port 2016.

While checking "netstat -an | grep 2016", no process is running on 2016.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms