1. Database type: Select the co-managed Oracle Database cloud solution on which the Oracle Database is running.
2. Depending on the option selected in the previous step, one of the following options is displayed:
   • Database system (for Bare Metal and Virtual Machine DB systems): Select the Bare Metal or Virtual Machine DB system. By default, the compartment selected on the Managed databases page is displayed, however, you can click Change compartment and select another compartment, if required.
   • VM cluster (for Exadata Cloud Infrastructure): Select the cloud VM cluster that provides a link between the Exadata Cloud Infrastructure resource and the 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.
3. Database home: Select the database home associated with the Oracle Cloud Database.
4. Pluggable database: Select this check box if you're enabling Database Management for a PDB.
   Note
   
   

   • If you're enabling Database Management for a PDB, then it must first be enabled on the associated CDB with the Full management option.
   • You can enable Database Management for a maximum of 10 PDBs in one CDB. If you want to increase the PDB limit, contact Oracle Support.
5. Database name: Select the Oracle Cloud Database. If you're enabling Database Management for a PDB, then you must select the associated CDB in this field.
6. Pluggable database name: Select the PDB. This field is only displayed if you're enabling Database Management for a PDB.
7. Service name: The unique service name in the Database_Name.Host_Domain_Name format is automatically displayed, however, you can edit it, if required.
8. Protocol: Select either the TCP or TCPS protocol to connect to the Oracle Cloud Database. By default, the TCP protocol is selected.
   Note
   
   If Oracle Data Guard is enabled on a Bare Metal or Virtual Machine DB system after Database Management was enabled for it using the TCPS protocol, then TCPS will have to be reconfigured. Enabling Oracle Data Guard is causing TCPS configuration to be overwritten, and it's recommended that TCPS is configured on a Bare Metal or Virtual Machine DB system after enabling Oracle Data Guard.

   Also, Database Management currently does not support Oracle Data Guard configuration and Database Management features are not available for standby databases.

9. Port: Specify the port number. If TCP is selected in the Protocol field, then port number 1521 is displayed by default and you can change it, if required.
10. Database wallet secret: Select the secret that contains the database wallet from the drop-down list. This field is only displayed if TCPS is selected in the Protocol field. If an existing database wallet secret is not available, then select Create new secret... in the drop-down list. The Create database wallet secret panel is displayed and you can create a new secret. For information on database wallets and how to create a secret in the Vault service, see Oracle Cloud 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:

    • Vault service permissions, see Permissions Required to Enable Database Management for Oracle Cloud Databases.
    • IAM policies, see Managing Policies.

1. Database user name: Enter the database user name.
2. Database 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 Oracle Cloud 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:

   • Vault service permissions required to use existing secrets or create new secrets, see Permissions Required to Enable Database Management for Oracle Cloud Databases.
   • IAM policies, see Managing Policies.

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 single instance Oracle Cloud Databases in the Bare Metal and Virtual Machine DB systems.
• Private endpoint for RAC Oracle Cloud Databases in the Virtual Machine DB system and Exadata Cloud 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 information on management options, see About Management Options.