Doc ID 1933649.1, MGMTDB and MGMTLSNR should not be monitored.
$ grep oms /etc/oratab oms:/u01/middleware/13.2.0:N $ . oraenv <<< oms $ emcli login -username=SYSMAN Enter password : Login successful $ emcli sync Synchronized successfully $ emcli get_targets -targets=oracle_listener -format=name:csv|grep -i MGMT 1,Up,oracle_listener,MGMTLSNR_host01 $ emcli delete_target -name="MGMTLSNR_host01" -type="oracle_listener" Target "MGMTLSNR_host01:oracle_listener" deleted successfully $ emcli sync $ emcli get_targets|grep -i MGMT
Note: MGMTDB was not monitored and can be deleted as follow:
$ emcli get_targets -targets=oracle_database -format=name:csv|grep -i MGMT $ emcli delete_target -name="MGMTDB_host01" -type="oracle_database"
The problem with monitoring MGMTDB and MGMTLSNR is getting silly page when they are relocated to a new host.
Host=host01 Target type=Listener Target name=MGMTLSNR_host01 Categories=Availability Message=The listener is down:
Dealing with the same issue for scan listener and have not reached an agreement to have them deleted as I and a few others think they should not be monitored.
Unfortunately, there is no official Oracle documentation for this.
Here’s a typical page for when all scan listeners are running from only one node.
Host=host01 Target type=Listener Target name=LISTENER_SCAN2_cluster Categories=Availability Message=The listener is down: $ srvctl status scan_listener SCAN Listener LISTENER_SCAN1 is enabled SCAN listener LISTENER_SCAN1 is running on node node02 SCAN Listener LISTENER_SCAN2 is enabled SCAN listener LISTENER_SCAN2 is running on node node02 SCAN Listener LISTENER_SCAN3 is enabled SCAN listener LISTENER_SCAN3 is running on node node02
