Database Server Generated Alerts and Enterprise Manager

You installed Oracle Enterprise Manager Cloud Control, added your production databases to the Enterprise Manager system. You set up the metric thresholds, monitoring templates and notification rules. Everything was looking OK until you got a warning email about “Current Open Cursors Count”. It was surprising because you didn’t set any threshold for it.

You checked the “Metric and Collection Settings” page to be sure that you didn’t set up any threshold, and you were right!

You wanted to edit the metric from the event details page, and all you got is “The metric data can not be found.” error. So what is happening?

EMCLI: Add a Database Target with Specific DB System Name

On Oracle Community forum, I’ve seen a good question about using EMCLI to add targets. The forum user says that they decided to name the database targets with combining db_name and hostname. As you may know, when you add a database target, EM also creates a database system for the new target (or assign it with an existing one). The new database system’s name is generated by adding “_sys” to the database target name. Let’s we add a database target named TEST, EM will create a database system as TEST_sys. If we name our database target as “”, EM will create a database system named “TEST_test.gokhanatil.com_sys”.

In my personal opinion, Enterprise Manager provides enough flexibility to report these information so I wouldn’t use this kind of naming system but that’s not the point. As you see, it works well for stand alone databases but when you add a standby database to this system, it becomes confusing. For example, your will be part of TEST_test.gokhanatil.com_sys. So the forum user asks if we can give a specific name to the database system instead of default naming. For example, our database system will be named as TEST_sys although its members are and

EM13c: OMSCA Recovery Mode Parameters “-as” and “-ms”

In the official backup and recovery documents of Oracle Enterprise Manager Cloud Control, when omsca tool is used for recovery, it is used with “-as” and “-ms” parameters but they are not well documented. For example:

[box type=”shadow”]Run omsca in recovery mode specifying the export file taken earlier to configure the OMS:

<OMS_HOME>/bin/omsca recover –as –ms –nostart –backup_file <exportconfig file>[/box]

Some parameters have no need any explanation but what are “-as” and “-ms”? Can we use them separately?

-AS means we want to recover the “OMS weblogic admin server”. The admin server operates as the central control entity for the configuration of the entire Enterprise Manager domain.

-MS means we want to recover the managed server hosting Oracle Management Service (OMS). It’s a mandatory parameter for recovery operations!

It’s possible to recover managed servers without recovering admin server of EM13c. For example, if you have Multi OMS site and lost one of your additional OMS, you can recover it with “-ms” parameter.

If you need to recover admin server, you also need to recover the managed server on the host, so you should use “-as” and “-ms” parameters together.

EM13c: How to Disable Autodiscovery (and Autopromotion) of Clusterware Managed Targets

After we upgraded EM13c, I encountered a problem about automatically promoted listener targets. Since EM12c, I do not add/promote listeners. In earlier versions of EM12c, I had weird problems while monitoring listeners on RAC systems (such as they are detected down although they’re up). Since then, I don’t monitor them (specially SCAN listeners). In EM12c, when I remove a listener, it doesn’t promoted again. With EM13c, I see that listeners are discovered and promoted automatically on each day. First I though, one of my team members accidentally add them, but then I see that it’s an automatic process. After a quick search on MoS, I didn’t find anything and opened a service request. After several mails, Oracle support staff told me that it’s an expected behavior, and I need to disable “autodiscovery” to prevent it (Doc ID 1522674.1) – I really don’t know how I couldn’t find it by myself, but even Oracle support guys spent 3 weeks to find the note 🙂

Which Management Packs are Required for Using the Notifications Feature from Cloud Control?

Sending notification emails shouldn’t require any licenses right? Unfortunately it might be more complicated than it seems

As you know Enterprise Manager Cloud Control provides a web interface called web console, and (naturally) it consists of web pages that enables you to access the features of Enterprise Manager Framework. Some of these features (mostly the basic ones) are free but some of them require you to buy management pack licenses. When you’re not sure if the page you accessed requires a management pack license, you can check it by clicking “Packs for this Page” (setup > management packs). It will show you a popup and list the required management packs. It’s also possible to enable annotations. When annotations are enabled, Enterprise Manager indicates licensed links by showing an abbreviation for a pack beside the licensed link. I noticed that there’s an interesting problem with using the notification feature of Enterprise Manager. In EM12c, when you check the required licenses for the notification feature/page, you’ll see that it requires almost all management packages. And according to the My Oracle Support Doc ID 1936531.1, the required management packs for notifications feature are listed correctly!