EM 12c, EM 13c: How to Create an emcli Script to Add Databases Based on the Targets Found in Auto Discovery Results in Enterprise Manager 12c and 13c Cloud Control
Last updated on APRIL 25, 2017
Applies to:Enterprise Manager for Oracle Database - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Up to Enterprise Manager Cloud Control Release 188.8.131.52, there is no method of 'mass promotion' in Enterprise Manager 12c Cloud Control. This means that if lots of databases are discovered on a particular node, it is necessary to go into auto discovery results, and promote each database individually. This can be time consuming, and there is an internal Enhancement Request raised on this.
Beginning with 184.108.40.206 Cloud Control and higher, you can mass promote database by selecting the option "Specify Common Monitoring Credential" from the page" Promote Database Discovered Targets". Then you can select 'all' or a set of discovered databases to be promoted in one operation.
If you cannot upgrade to 220.127.116.11, the fastest way to promote a database would be to use the emcli add target command. However, the user would have to manually create the script to add the database targets in the first place. The script requires details such as hostname, port, sid,oracle_home of the database.
The goal of this document is to provide a quick way of creating the emcli add target script. The relevant details of the databases which have been discovered in auto discovery results will be used to create the emcli script. In this example the dbsnmp password will be hardcoded into the script as 'dbsnmp'. It can be changed appropriately once the script has been created
In addition to the method outlined in this article, Oracle now provides an example script 'promote_discovered_dbs.py' which is documented in the Enterprise Manager Command Line Interface (emcli) guide, which is also able to promote the un-managed databases. See:
for more information on this. Please note that this only applies to the single instance database target and not to cluster databases or listeners.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms