New EMCLI Verbs in Enterprise Manager 12c R4 (

Today I see Ray Smith’s blog post about EM CLI Verb Changes. He provided a quick list of several new and deprecated EMCLI verbs in Enterprise Manager 12c R4. Pete Sharman commented on the blog post and said there are missing verbs. Ray said he made the list based on Oracle Documentation. So I decided to make another list based on EMCLI HELP output. Here’s the list of new EMCLI verbs:

  • invoke_ws: Invokes EM web service.

Agent Update Verbs:

  • get_agent_update_status: Shows Agent Update Results using Gold Image.
  • get_not_updatable_agents: Shows agents which can not be updated
  • get_updatable_agents: Shows updatable Agents for a given gold agent image name or series
  • update_agents:  performs Agent Update Prereqs and submits Agent Update Job

BI Publisher Reports Verbs:

  • grant_bipublisher_roles: Grants access to the BI Publisher catalog and features.
  • revoke_bipublisher_roles: Revokes access to the BI Publisher catalog and features.

Blackout Verbs:

  • create_rbk: Creates Retro-active blackout on given targets and updates their availability. The retro-active blackout feature needs to be enabled from the UI for using this emcli command.

CFW Verbs:

  • cancel_cloud_service_requests: Cancel the cloud requests. Either user or names option should be provided.
  • delete_cloud_service_instances: Deletes the cloud service instances based on the specified filter.
  • delete_cloud_user_objects: Deletes cloud user objects including cloud service instances and requests.
  • get_cloud_service_instances: Retrieves the list of cloud service instances. All Instances will be printed if no option is specified.
  • get_cloud_service_requests: Retrieves the list of cloud requests. All requests will be printed if no filter is applied.
  • get_cloud_user_objects: Retrieves the list of cloud user objects including cloud service instances & requests. All objects will be printed if user option is not used.

Compliance Verbs:

  • fix_compliance_state: Fix compliance state by removing references in deleted targets.

Deployment Procedure Verbs:

  • get_runtime_data: Download execution runtime properties data. The execution can be retrieved by using either instance GUID, or execution GUID or name value pair.

Upgrading Enterprise Manager Cloud Control to

Enterprise Manager Cloud Control is released yesterday, and I have downloaded it immediately to upgrade our system. It was a very smooth process. The version of our Enterprise Manager was Enterprise Manager is compatible with agents, so total downtime was about 30 minutes (of course it depends on your hardware). I upgraded our system using “one system upgrade” option and then upgraded all EM agents. Only a few agents are failed to upgrade, and I remember that we also had problems when deploying those agents. In this blog post, I will go through the whole process step by step.

I recommend you to read the official upgrade documentation (Thanks to Brandon to remind me to write this). As a blogger, I share my own experience. I can not guarantee that these steps will work on your environment, so you should always check the official documentation first.

As usual, you can download the new version from Oracle website. You need to download all 3 zip files to your server, create a directory and unzip them all into this directory:

Before you run the installer, we need to prepare our system for upgrading. Run emctl to copy EMKey from emkey.ora file to the management repository database:

Enter weblogic admin password as Admin User’s password and SYSMAN password for EM root password. The EMKey will be copied to the Management Repository (it will be removed automatically by the installer after the upgrade is done). Now shutdown the OMS:

Enterprise Manager 12c: Be Careful About Naming DB Systems

Yesterday, we added a development database to our EM12c system. About 15 minutes later, the incident management flooded us with alert mails about newly added database. Unfortunately its SID was same with our production DB, and when adding the database, my colleague didn’t change its name and accepted the defaults. I was out of office when I got those mails, after a short panic, I called my colleague to check the situation and she said it’s just the development database. We decided to remove development database from the Enterprise Manager, and add it again with another name.

I went to the target’s home page, clicked remove target under target setup menu. The Enterprise Manager warned me about it will delete the database and its related targets (a Database System). I clicked YES, and my colleague asked me why I removed the production database from Enterprise Manager! As a DBA, we are usually very careful when doing something, and I was sure that I removed the correct database. I checked the databases and saw that both PROD and DEV databases are gone. Of course, we added the production database again quickly, and then I started to investigate the situation. After examining PL/SQL codes of MGMT_ADMIN package, and doing more add-remove tests, I see that it’s all about the DB systems. Here are the records in MGMT_TARGETS_DELETE (it’s a table which is used by EM to store deleted targets):


Oracle Enterprise Manager Cloud Control 12c Plugin for PostgreSQL

In my company, we use PostgreSQL, Postgres Plus (a commercial fork of PostgreSQL provided by EnterpriseDB) beside Oracle databases. Unfortunately different databases need different tools to monitor, and implementing a standard monitoring procedure for all databases becomes a real problem. Good thing is Oracle Enterprise Manager is an extendable software supporting 3rd party plugins, and there are companies like Blue Medora which focuses on the product enhancements for Enterprise Manager. Blue Medora released a plugin to monitor PostgreSQL for Oracle Enterprise Manager, and I just deployed it to our servers. In this blog post, I’ll try to give brief instructions to set up the plugin.

First you need to download the plugin from Blue Medora website. I do not know when it will be added to self-update of Enterprise Manager but for now, you need to downloaded it manually. After you download the zip file, copy the zip file to your Enterprise Manager 12c server, and unzip it. I unzip it to a folder called postgre_plugin (under home directory of oracle user):

The zip contains a file named “bm.em.xpgs_12.”. It’s the plugin file which we’ll need to import to Enterprise Manager. We’ll use “emcli” to login to Enterprise Manager, and then import the plugin:

I divided the last command to two lines, using \ symbol, so it fits into the code-window on my website but you may write it one line (without \ symbol).

Plugin imported

EMDIAG Repvfy Kit for Oracle Enterprise Manager Cloud Control 12c

EMDIAG Repvfy is a tool which is designed to collect data from a Cloud Control Management Repository to assist in the diagnosis and optimization of EM12c. It’s mentioned on “Oracle Enterprise Manager 12c Configuration Best Practices (Doc ID 1553342.1)”, and you can find the required information on Doc ID 1426973.1, to download, install and run EMDIAG Repvfy. Yesterday, I installed it for our EM12c system, and I got some errors while running it. So here is a quick blog post about EMDIAG Repvfy.

At first, to be able to install (and run) it, you should set Oracle environment variables for Enterprise Manager Cloud Control repository database. You should also set EMDIAG_HOME variable which will point to the folder you unzipped the tool. So you run the following commands to install EMDIAG Repvfy:

I tried to run it with “execute optimize” parameter, but it gave some errors when running: