Discover Autonomous Databases as Non-host Targets Using the Guided Process

Autonomous Databases are treated as non-host targets in Oracle Enterprise Manager and can be discovered using the guided process.

Using the guided process, you can discover multiple Autonomous Databases at the same time, use the advanced search functionality to filter and search for Autonomous Databases, and navigate through Oracle Cloud Infrastructure regions and compartments in the Oracle Enterprise Manager console.
Before you start the guided process to discover Autonomous Databases, you must:
  • Define a global named credential for your Oracle Cloud Infrastructure account. On defining the global named credential, it is recommended that you test if it is successful in establishing a connection with Oracle Cloud Infrastructure. For information, see:
  • Ensure that you have the permissions to modify content in $INSTANCE_HOME/sysman. As part of the guided process to discover Autonomous Databases, the OCI Client Credential (Wallet) .zip file that contains the credentials to access data in the Autonomous Database is downloaded and saved in $INSTANCE_HOME/sysman/tmp/.
To discover an Autonomous Database as a non-host target using the guided process:
  1. Open the navigation menu, from the Setup menu, select Add Target, and then select Add Targets Manually.
  2. On the Add Targets Manually page, click Add Using Guided Process on the Add Non-Host Targets Using Guided Process tile.
  3. In the Add Using Guided Process dialog box, select Autonomous Databases and click Add.
    The Autonomous Database Discovery page is displayed.
  4. Provide the following details to search for the Autonomous Database:
    1. EM Agent: Select the Oracle Enterprise Manager agent you will be using to discover the Autonomous Database.

      Note:

      A standby agent is not supported when the primary agent is a remote agent.
    2. Oracle Cloud Infrastructure Credentials: Select the named credentials associated with your Oracle Cloud Infrastructure account.
    3. OCI Home Region Identifier: Select the Oracle Cloud Infrastructure home region in which your tenancy is provisioned.
    4. OCI Subscribed Regions: Select the subscribed regions where you want to perform the discovery. When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy in the Home region, which contains the account information and the identity resources. The subscribed regions are regions to which you have subscribed to access resources in a different geographical location. The options listed in this drop-down are updated based on the selection of the agent, named credentials, and the home region.
    5. Use Advanced Search Filter (Optional): Enable this switch for a more precise filtering of Autonomous Databases. Specify the filter condition that will be used with the core query statement, which is already provided. Note that using advanced search will overwrite the Oracle Cloud Infrastructure attributes, compartment and tags and directly display the Autonomous Databases specified in the syntax. For information on how to construct filter conditions, see Search Language Syntax: Conditions.
    6. OCI Compartment: Select the compartment in which the Autonomous Databases reside.
    7. Child Compartments: Enable this switch if you want to display the Autonomous Databases in the child compartments of the selected compartment.
    8. OCI Attributes: Select Autonomous Database deployment and workload types:
      1. Deployment Type: Select Autonomous Database deployment types:
        • Dedicated: Infrastructure that offers a private cloud in the public cloud, a completely dedicated compute, storage, network and database service.
        • Serverless: Infrastructure where you provision and manage only the Autonomous Database, while Oracle deploys and manages all the underlying infrastructure.
      2. Workload Type: Select Autonomous Database workload types:
        • Transaction Processing: Tailored primarily for complex Transaction Processing workloads that include operational reporting and batch data processing.
        • Data Warehouse: Tailored for Data Warehouse and related workloads including Data Marts, Machine Learning or as part of a Data Lake deployment.
    9. OCI Tags: Add the Oracle Cloud Infrastructure tags associated with the Autonomous Database, if any.

      Note:

      Only defined tags are supported and can be added.

      For information on tags, see Overview of Tagging.

    10. Click Next.

      The Summary Results message with information on the number of Autonomous Databases in the compartment is displayed.

    11. Click Continue in the Summary Results message.
  5. Select the Autonomous Databases that you want to discover and set the following for each selected database:
    1. Use one of the following options to provide the monitoring user and password for each selected Autonomous Database:
      • Click Set Credentials and Groups, enter the Monitoring User and Monitoring Password, and click Confirm and Test. If you have created a named credential to store the monitoring user and password, then you can select the Use Existing Named Credential check box and use it instead. Optionally, you can also select a Group Membership to add the selected Autonomous Database to one or more existing groups. For information on groups, see Introduction to Groups in Oracle Enterprise Manager Monitoring Guide.
      • Double-click the database row in the table, edit the Monitoring User and Monitoring Password fields and click the Confirm and Test icon (Confirm and Test) in the Action column.
    2. Optionally, click Set Global Target Properties, set the properties for the selected Autonomous Databases, and click OK.
  6. Click Review.
  7. Review the Autonomous Databases that are going to be discovered as targets in Oracle Enterprise Manager and click Submit.
After you have discovered the Autonomous Databases in Oracle Enterprise Manager, you can verify if the discovery was successful by opening the navigation menu and from the Targets menu selecting the Databases option. The Autonomous Databases you discovered should be listed on the Databases page.