1. Database type: Ensure that the correct Oracle Database cloud solution is selected.
2. Depending on the option selected in the previous step, one of the following options is displayed:
   • Database system (for Base Database Service): Select the DB system in the Base Database Service. 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 ExaDB-D, ExaDB-XS, and ExaDB-C@C): Select the cloud VM cluster that provides a link between the ExaDB-D, ExaDB-XS, or ExaDB-C@C 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. Database name: Select the Oracle Cloud Database.
5. If you want to enable Diagnostics & Management for a CDB or PDB, select one of the following options:
   • Diagnostics & Management for a CDB:
     • Enable Diagnostics & Management for CDB and all PDBs: Select to enable Diagnostics & Management for a CDB and all its associated PDBs at the same time. A database common user created at the CDB level with the CONTAINER=ALL privilege is required to bulk enable Diagnostics & Management. Using this option allows for the collection of metrics at the CDB level, without having to connect to each PDB. For information on the SQL script to create a database common user with the required privileges, see Creating the Oracle Database Monitoring Credentials for Database Management (KB57458) in My Oracle Support.
     • Enable Diagnostics & Management for CDB only: Select to enable Diagnostics & Management for a single CDB.
   • Diagnostics & Management for PDBs:
     • Enable Diagnostics & Management for all PDBs: Select to enable Diagnostics & Management for all the PDBs associated with a Diagnostics & Management-enabled CDB. A database common user created at the CDB level with the CONTAINER=ALL privilege is required to bulk enable Diagnostics & Management. Using this option allows for the collection of metrics at the CDB level, without having to connect to each PDB. For information on the SQL script to create a database common user with the required privileges, see Creating the Oracle Database Monitoring Credentials for Database Management (KB57458) in My Oracle Support.
     • Enable Diagnostics & Management for a single PDB: Select to enable Diagnostics & Management for a single PDB associated with a Diagnostics & Management-enabled CDB, and select the PDB in the Pluggable database name drop-down list.
   Note
   
   

   • For Oracle Cloud Databases, Diagnostics & Management only supports the monitoring and management of PDBs for Oracle Database version 19c and later.
   • If you're enabling Diagnostics & Management for PDBs, then it must be enabled on the associated CDB with the Full management option.
   • If you're bulk enabling Diagnostics & Management for all the PDBs associated with a CDB, there's no limit to the number of PDBs for which it can be enabled. However, if you're enabling Diagnostics & Management for a single PDB, you can only enable it for a maximum of 10 PDBs in one CDB, and to increase the PDB limit, contact Oracle Support.
   • If the collection of metrics is at the PDB level, you can change metric collection to the CDB level by disabling Diagnostics & Management for the CDB and then re-enabling it for the CDB and its PDBs. This requires a database common user created at the CDB level with the CONTAINER=ALL privilege.
6. Service name: The unique service name in the Database_Name.Host_Domain_Name format is automatically displayed, however, you can edit it, if required.
7. 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 DB system in the Base Database Service after Diagnostics & Management was enabled for it using the TCPS protocol, then TCPS will have to be reconfigured. Enabling Data Guard is causing TCPS configuration to be overwritten, and it's recommended that TCPS is configured on the DB system after enabling Data Guard.
8. Port: Enter 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.
9. 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 Oracle Cloud Infrastructure Vault service, see Oracle Cloud Database-related Prerequisite Tasks.

   Note that a resource principal policy is required to grant Managed Database resources the permission to access the secret that contains the database wallet. If the policy is not created, then A 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_Resource_Policy in the IAM service.

   For information on:

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

1. Database user name: Enter the database user name.
   Note
   
   

   • If you're enabling Diagnostics & Management for a database in an Oracle Data Guard configuration that contains a physical standby database in mounted state, you must ensure that the monitoring user has the SYSDG privilege. If the SYSDG privilege is not granted to the monitoring user, metric collection may stop for the new standby databases following a role switchover or failover.
   • Diagnostics & Management is not supported for a physical standby database in mounted state if a Management Agent is used to enable Diagnostics & Management.
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 Oracle Cloud Database-related Prerequisite Tasks.

   Note that a resource principal policy is required to grant Managed Database resources the permission to access the secret that contains the database user password. If the policy is not created, then A 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_Resource_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 Diagnostics & Management for Oracle Cloud Databases.
   • IAM policies, see Managing Policies.

• Private Endpoint (for Base Database Service, ExaDB-D, and ExaDB-XS): Select the private endpoint that will act as a representation of Database Management in the VCN in which the Oracle Cloud 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:

  • Private endpoint for single instance Oracle Cloud Databases in the Base Database Service.
  • Private endpoint for RAC Oracle Cloud Databases in the Base Database Service, ExaDB-D, and ExaDB-XS.

  If an existing Database Management private endpoint is not available, then select Create private endpoint... in the drop-down list to create one. For information on how to create a private endpoint, see Create a Database Management Private Endpoint for Oracle Cloud Databases.

  If ingress and egress security rules were not added to an NSG or a Security List as part of the prerequisite tasks, click Add network security rule.

  The security rules are required to enable communication between Diagnostics & Management and the Oracle Cloud Database. For information on the required Oracle Cloud Infrastructure Networking service permissions, see Permissions Required to Enable Diagnostics & Management for Oracle Cloud Databases.

  In the Add network security rule panel:

  1. Select either Security list or Network security group depending on which security feature you want to use to add security rules.

     Note that the Network security group radio button is only displayed if the Database Management private endpoint and the Oracle Cloud Database have an attached NSG.

  2. Select one of the following options in the Ingress rule section and review the details of the ingress rule that will be created:
     • If you've selected the Security list option, select a security list in the Oracle Cloud Database's subnet.
     • If you've selected the Network security group option, select an NSG attached to the Oracle Cloud Database.
  3. Select one of the following options in the Egress rule section and review the details of the egress rule that will be created:
     • If you've selected the Security list option, select a security list in the private endpoint's subnet.
     • If you've selected the Network security group option, select an NSG attached to the private endpoint.
  4. Click Submit.

  For general information on how to enable communication using security rules, see Enable Communication Between Database Management and Oracle Cloud Databases.

• Management Agent (for ExaDB-D and ExaDB-C@C): Select the Management Agent in the Management Agent ID drop-down list. If the compartment in which the Management Agent resides is different from the compartment displayed, then click Change compartment and select another compartment.
  Note
  
  

  • The same Management Agent that was used to enable Diagnostics & Management for a CDB is used when enabling Diagnostics & Management for its PDBs. For the collection of metrics at the CDB level, a Management Agent 240628.1505 or later is required.
  • If using a Management Agent when enabling Diagnostics & Management for ExaDB-D, you cannot edit Diagnostics & Management and select a different Management Agent later.

  If a Management Agent is not installed, then you must first install one. For generic information, see Install Management Agents and for additional information on how to install a Management Agent on Exadata Cloud to enable Diagnostics & Management, see Observability & Management Support For Exadata Cloud (PNEWS1338) in My Oracle Support.

For information on management options, see About Management Options.