Oracle Cloud Infrastructure Documentation

Enable Diagnostics & Management for Autonomous Databases

Before you enable Database Management Diagnostics & Management for Autonomous Databases, you must:

You can enable Diagnostics & Management for Autonomous Databases on the Autonomous Database details page or on the Administration Managed databases page in Database Management.

To enable Diagnostics & Management for Autonomous Databases in Database Management:

  1. Sign in to the Oracle Cloud Infrastructure console.
  2. At the top of the page, ensure that the region in which you want to enable Diagnostics & Management is selected.
    Note

    Cross-region monitoring and management of Oracle Databases is not available.
  3. Open the navigation menu, click Observability & Management. Under Database Management, click Administration.
  4. On the left pane, select a compartment in the Compartment drop-down list and Autonomous in the Deployment type drop-down list.
  5. On the Managed databases page, click Enable Database Management.
  6. In the Enable Database Management panel:
    1. Specify the following details to select a database:
      1. Database type: Select Autonomous.
      2. Workload type: Select the Autonomous Database workload type.
      3. Deployment type: Select the Autonomous Database deployment type: Autonomous Serverless or Autonomous Dedicated.
      4. Autonomous Database: Select the Autonomous Database. By default, the compartment selected on the Managed databases page is displayed, however, you can click Change compartment and select another compartment, if required.
      5. Service name: The predefined connection profiles for the Autonomous Database are automatically displayed in the dbname_<service name> (TLS or Mutual TLS) format. The default selection is displayed in the Service name field, however, you can select another option, if required. Note that if mTLS is appended to the service name, then the Database wallet secret field is displayed and you will have to upload the wallet.
      6. Protocol: The TCP or TCPS protocol used to connect to the Autonomous Database is displayed based on the previously selected predefined service name and cannot be edited.
      7. Port: The port number is displayed based on the previously selected predefined service name and cannot be edited.
      8. Database wallet secret: Select the secret that contains the wallet from the drop-down list. This field is only displayed if mTLS is appended to the service name. If an existing secret that contains the wallet is not available, then select Create new secret... in the drop-down list and save the cwallet.sso file in a secret. For information on database wallets and how to create a secret in the Vault service, see Autonomous Database-related Prerequisite Tasks.

        Note that a service policy is required to grant Database Management (dpd) the permission to read the secret that contains the database wallet. If the service policy is not created, then the Service policy is required... message is displayed and you can click Add policy to view and automatically add it. The Oracle Cloud Infrastructure IAM service creates the policy and it's added to a collection of policies called DBMgmt_Service_Policy in the IAM service.

        For information on:

    2. Specify the database credentials for the connection to the selected Autonomous Database.
      1. Database user name: Enter the database user name.
      2. User password secret: Select the secret that contains the database user password from the drop-down list. If the compartment in which the secret resides is different from the compartment displayed, then click Change compartment and select another compartment.

        If an existing secret with the database user password is not available, then select Create new secret... in the drop-down list. The Create password secret panel is displayed and you can create a new secret. For information on database monitoring user credentials and how to save the database user password as a secret in the Vault service, see Autonomous Database-related Prerequisite Tasks.

        Note that a service policy is required to grant Database Management (dpd) the permission to read the secret that contains the database user password. If the service policy is not created, then the Service policy is required... message is displayed and you can click Add policy to view and automatically add it. The IAM service creates the policy and it's added to a collection of policies called DBMgmt_Service_Policy in the IAM service.

        For information on:

    3. Select the private endpoint in the Private endpoint drop-down list, which will act as a representation of Database Management in the VCN in which the Autonomous Database can be accessed. If the compartment in which the private endpoint resides is different from the compartment displayed, then click Change compartment and select another compartment.

      You must ensure that the appropriate Database Management private endpoint is available. Here are the two types of Database Management private endpoints:

      • Private endpoint for Autonomous Databases Serverless
      • Private endpoint for Autonomous Databases on Dedicated Exadata Infrastructure

      If a Database Management private endpoint is not available, then you must create one. For information on how to create a private endpoint, see Create a Database Management Private Endpoint for Autonomous Databases.

      Note

      The Private endpoint information section in the Enable Database Management panel is not displayed if the Secure access from everywhere option is used to configure network access to an Autonomous Database Serverless.
    4. Click Enable Database Management.
A confirmation message with a link to the Work requests section on the Autonomous Database details page is displayed. Click the link to monitor the progress of the work request.

You can verify if Database Management is successfully enabled on the following pages:

  • Managed databases page in Database Management: On the left pane, select the compartment in which the Autonomous Database resides and select Autonomous in the Deployment type drop-down list. After Database Management is enabled, the Autonomous Database is listed as a Managed Database. To disable Database Management, click the Actions icon (Actions) for the Autonomous Database and click Disable Database Management.
  • Autonomous Database details page of the Autonomous Database: Verify if the Enable option next to Database Management is replaced with Enabled. A Disable option is also displayed, which you can click to disable Database Management.
Note

If you enabled Diagnostics & Management for Autonomous Databases in Database Management prior to the availability of the advanced monitoring support for Autonomous Databases or on the Autonomous Database details page, you must provide the connection information to use the monitoring and management features. To do so:
  1. Go to the Administration Managed databases page in Database Management.
  2. Click the Actions icon (Actions) for the Autonomous Database and click Edit Database Management.