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 the emd.properties file or you can use the OEM console to modify it.
The OEM console can submit a job called “Agents Configuration Operation”. This job is going to prompt you for a name and the agents you want to modify the property. The Parameters tab has all the available parameters to modify. Just set the EM_MONITOR_ALL_DISKS to true and submit the job.

If you want to modify this manually. Just follow the instruction in the MOS note 1513537.1.

Exclusion not working in OEM 13c Rule Sets

While setting up Rules and RuleSets you may want to exclude either target types or alert categories from your notifications. Well, there’s an issue if you try to do this in OEM 13c.
If you configure a Rule that has the exclusion and contains more than one category, then you will keep receiving alerts from it. So the exclusion won’t work.
In order to fix it you need to apply a patch or the January 2018 BP for OEM.
MOS note (Doc ID 2347238.1) shall be used as a reference.

Install OMC Data Collector To Harvest Oracle Enterprise Manager Target’s Metric Data

In order to make use of the data you already have in your Oracle Enterprise Manager (OEM) in Oracle’s Management Cloud (OMC) you need to install and configure the OMC’s Data Collector agent.
Here’s how you do it.
Login to OMC and navigate to Administration -> Agents -> Download
In the Agent Type box, select Data Collector.

Select the desired Operating System version. In my case is Linux 64 bit.

Once the agent is downloaded, take a note in the same OMC’s web page of the TENANT_ID and the UPLOAD_ROOT values.
Next login to the server hosting your OEM Repository database.
Create a directory in a place where you have enough space (3GB).
$ cd /u01/agent
$ mkdir omc
$ cd omc
Transfer the downloaded file to this new directory and unzip it.
$ ls
$ unzip datacollector_linux.x64_1.23.0.zip
Archive:  datacollector_linux.x64_1.23.0.zip
  inflating: unzip
  inflating: AgentDeployment.sh
  inflating: agentimage.properties
  inflating: agent.rsp
  inflating: agent_software_build.xml
 extracting: agentcoreimage.zip
  inflating: AgentInstall.sh
Modify the response file adding the required values. This step depends in whether you’re using a Gateway or a Proxy to connect to the OMC.
$ vi agent.rsp
All required values can be found here.
Now execute the installation.
$ ./AgentInstall.sh
Unzipping agent software, this may take some time…
Installing Data Collector…
Data Collector parameter validation started…
Skipping Data Collector pre-requisite checks as IGNORE_VALIDATIONS is set to true…
Data Collector base directory creation started…
Security artifacts download started…
Data Collector setup started…
Registering Data Collector…
Starting Data Collector…
Data Collector started.
Data Collector installation completed.
The following configuration scripts need to be executed as the root user:
/bin/sh /u01/agent/omc/datacollector/core/1.23.0/root.sh
You now need to execute the configuration script as root.
Once this is executed, go and verify the Data Collector agent is up and running.
$ cd /u01/agent/omc/datacollector/agent_inst/bin
./omcli status agent
Oracle Management Cloud Data Collector
Copyright (c) 1996, 2017 Oracle Corporation.  All rights reserved.
Version                : 1.23.0
Started at             : 2017-04-07 11:45:04
Started by user        : oracle
Operating System       : Linux version 4.1.17-12.3.5.el6uek.x86_64 (amd64)
Data Collector enabled : true
Sender Status          : FUNCTIONAL
Gateway Upload Status  : FUNCTIONAL
Last successful upload : 2017-04-07 11:46:28
Last attempted upload  : 2017-04-07 11:46:27
Pending Files (MB)     : 2.26
Pending Files          : 80
Backoff Expiration     : (none)
Agent is Running and Ready
Verify the OMC’s Data Collector in the OMC console.
Navigate to Agents -> Administration -> Data Collectors
In this page you should see your newly installed Data Collector Agent.


I remember seeing this hidden parameter in the past ( and that had an issue when querying v$temp_extent_map view. 
This view returned wrong results if this parameter was set to true.
Now is a different story in 
We started to see many ORA-600 [kkqcscpopnWithMap: 0] errors. 
Turns out is because of the same parameter.
MOS note “Query Errors With ORA-600 [kkqcscpopnWithMap: 0] (Doc ID 2260457.1)" gives a workaround and a patch to be applied.
After applying the patch no more errors in the alert log.

This patch is non-Data Guard Standby-First Installable

During a DB patching I found this note in the patch README file.
This patch is non-Data Guard Standby-First Installable - 
Please read My Oracle Support Note 1265700.1 
This is the first time I see this, so I was curious about this as Oracle recommends to apply the patches first to the standby database and then patch the primary database.
After reading the note id 1265700.1, found that we must shutdown both the primary and the standby and apply the patches at the same time.
This worked well and both databases were patched.