Target MGMTLSNR or MGMTDB Down in OEM

Hello!
After discover your new 12c targets you are facing target status down for MGMT targets, similar to image below?

mgmt_targets

And checking on server all looks to be ok, right?

[root@server ~]# ps -ef |grep smon |grep MGMT
root 6188 6120 0 16:00 pts/0 00:00:00 grep --color=auto smon
oracle 22835 1 0 Nov30 ? 00:00:25 mdb_smon_-MGMTDB
[root@server ~]#
[root@server ~]# ps -ef |grep lsnr |grep MGMT
root 6598 6120 0 16:01 pts/0 00:00:00 grep --color=auto lsnr
oracle 22363 1 0 Nov30 ? 00:00:16 /u01/app/grid/12.1.0.2/bin/tnslsnr MGMTLSNR -no_crs_notify -inherit
[root@server ~]# /u01/app/grid/12.1.0.2/bin/crsctl stat res -t |grep -i mgmt
--------------------------------------------------------------------------------
Name Target State Server State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.MGMTLSNR
1 ONLINE ONLINE server 1.1.1.1 10.1
0.10.10,STABLE
ora.mgmtdb
1 ONLINE ONLINE server Open,STABLE
--------------------------------------------------------------------------------
oracle:server@+ASM1 /u01/app/oracle: srvctl status listener -l MGMTLSNR
Listener MGMTLSNR is enabled
Listener MGMTLSNR is running on node(s): server
oracle:server@+ASM1 /u01/app/oracle: lsnrctl status MGMTLSNR
LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 16-DEC-2016 16:06:30
Copyright (c) 1991, 2014, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=MGMTLSNR)))
STATUS of the LISTENER
------------------------
Alias MGMTLSNR
Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production
Start Date 30-NOV-2016 08:45:17
Uptime 16 days 7 hr. 21 min. 13 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/grid/12.1.0.2/network/admin/listener.ora
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=MGMTLSNR)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=1.1.1.1)(PORT=1521)))
Services Summary...
Service "-MGMTDBXDB" has 1 instance(s).
Instance "-MGMTDB", status READY, has 1 handler(s) for this service...
Service "_mgmtdb" has 1 instance(s).
Instance "-MGMTDB", status READY, has 1 handler(s) for this service...
Service "lawsondev_clstr" has 1 instance(s).
Instance "-MGMTDB", status READY, has 1 handler(s) for this service...
The command completed successfully

Don’t worry. After some researching about the issue, I found the MOS: EM 12c: UNKNOWN Status for ‘-MGMTDB’ Database (GIMR database) in Enterprise Manager 12c Cloud Control after Failover to Different Node (Doc ID 1933649.1) indicating that MGMT targets should not be monitored on EM, as per:

The Grid Infrastructure Management Repository should not be monitor by Enterprise Manager Cloud Control 12c. It is monitored by CRS and its configuration is managed with the mgmtca utility.
Please note that the same applies for MGMTLSNR target. MGMTLSNR target should not be monitored by Enterprise Manager Cloud Control.

This way, I’d recommend you to remove this targets from OEM. Simple like that.

See you!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s