Oracle Enterprise Manager 13.3 problems discovering Exadata targets

If you are on the latest Exadata plugin for EM 13.3 (well, even the 13.2 version of the plugin). Be aware that there’s a bug where if the Exadata nodes’ names are longer than 7 characters, you cannot discover them. EM just throws a weird error with below legend: SEVERE: makeTargetsXml for each rack#: 1… Continue reading Oracle Enterprise Manager 13.3 problems discovering Exadata targets

OEM 13c and Amazon’s RDS

Amazon released a note late last year about Amazon’s RDS is now supporting Oracle Enterprise Manager Agents.Amazon RDS supports agent version 12 (12.1.0.5), 13R1 and 13R2 (13.2.0.0).You can use this to monitor your DB instances running on Amazon’s RDB but there are some limitations, like the fact you cannot execute jobs against those targets.See below… Continue reading OEM 13c and Amazon’s RDS

Enable NFS mount point monitoring in OEM 13c

OEM doesn’t monitor NFS mount points by default. In case you need to monitor NFS mount points you have 2 options. Either create a metric extension using an OS script or to enable a property called EM_MONITOR_ALL_DISKS in the agent’s configuration file.There are two ways to accomplish the second option. You can go and modify… Continue reading Enable NFS mount point monitoring in OEM 13c

“Failed to find the OPatch patch directory” while applying patch 25105555 ( 13.2.0.0.161231) from OEM console

While applying patch 25105555 ( 13.2.0.0.161231) to an agent using the "provisioning and Patching" console from OEM 13.2 and choosing the "Upgrade OPatch" option, got this error:---------- Error Message ----------Error: 010Failed to find the OPatch patch directory "/tmp/p6880880_600000000057471_2000_0/oracle/OPatch". If you chose "No" for the "StagePatches" option, ensure that you manually place the patch at the… Continue reading “Failed to find the OPatch patch directory” while applying patch 25105555 ( 13.2.0.0.161231) from OEM console

2017 April PSU – OEM sending tablespace related alerts every collection schedule

I noticed that several alerts related to tablespace full were sent from OEM every collection schedule. At first sight I thought this may be related to OEM itself but after spending some significant time in MOS found a bug note stating that the 2017 April PSU patch was responsible.The issue is that dba_tablespace_usage_metrics is not accounting… Continue reading 2017 April PSU – OEM sending tablespace related alerts every collection schedule

OMS responded illegally [ERROR- Failed to Update Target Type Metadata] in 13c R2

I want to discuss about this OMS error coming from the agent’s heartbeat status. The agent shows with an unreachable status but is actually up and running.$: emctl status agentOracle Enterprise Manager Cloud Control 13c Release 2Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.---------------------------------------------------------------Agent Version          : 13.2.0.0.0OMS Version            : (unknown)…Last Reload            : (none)Last successful… Continue reading OMS responded illegally [ERROR- Failed to Update Target Type Metadata] in 13c R2