Add an Exadata Database Service on Cloud@Customer Database

Add Exadata Database Service on Cloud@Customer databases on the Database fleet administration page.

Before adding a database make sure you run the best practice script steps for Ops Insights databases outlined in OCI : Best Practices / Troubleshooting Guide For Monitoring Databases In Ops Insights (Article ID KB78518). It is strongly recommended the script be run every 6 months or if any databases are missing the storage or tablespace data.

1. Open the navigation menu, click Observability & Management, and then click Ops Insights.
2. In the left pane, click Administration, and then click Database fleet.

   The Database fleet administration page displays.

3. Click Add databases.
4. Under Telemetry, select Cloud Infrastructure.
5. In the Database type field, select Exadata Database Service on Cloud@Customer.
6. Select the Services to enable for the selected databases. Ops Insights and Database Management are displayed and can be enabled together.
   Note
   
   If a service is already enabled for the selected database, its enablement request is skipped.
7. In the Select database section, enter the required database selection information:
   1. VM cluster: Select the VM cluster compartment that contains the VM cluster, and then select the VM cluster.
   2. Database home: Select a database home (system or cluster). All database homes in the database system are available in the drop-down selector.
   3. Database: Select a database from the database home. Databases are identified as either container or non-container. If you select a CDB, you’ll be provided with the option of selecting all PDBs in the container or a single PDB.
      Note
      
      When PDBs are added or removed from the DB system or VM cluster, they will automatically be enabled or disabled:

      • When performing disable, select the CDB and disable that target alone. That will disable all the PDBs as well.
      • When performing a delete, select the CDB and delete that target alone. That will delete all the PDBs as well.
      • If you previously disabled the CDB (and thus all the PDBs) and want to re-enable Ops Insights, enable on the CDB resource only.
   4. Pluggable database (optional): When a CDB is selected, you can select all PDBs or a single PDB.

      If Database Management is selected, you must configure its enablement scope separately. Depending on the database and its current status, you can select from the following options:

      • Enable Diagnostics & Management for CDB and all PDBs
      • Enable Diagnostics & Management for CDB only
      • Enable Diagnostics & Management for all PDBs
      • Enable Diagnostics & Management for a single PDB

      This selection is independent of the Ops Insights PDB selection. For more information, see Enable Diagnostics & Management for Oracle Cloud Databases.

   5. Service name: If no PDB was specified above, enter the service name corresponding to the CDB. If one was specified, enter the service name corresponding to the specified PDB.
   6. Protocol: Select either TCP (default) or TCPS, depending on your configuration.
      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.
   7. Port: Enter the port number, the default Oracle recommended TCP port is 1521.
   8. TLS secret (only for TCPS): When using a TCPS connection protocol a TLS secret is required. Select the compartment that contains the secret and the corresponding secret from the drop-down list or click Create new TLS secret to create a new secret, the Create TLS secret panel appears.

      In the Create TLS secret panel, enter the following information:

      1. Name: Enter a name for the TLS secret.
      2. Description (optional): Enter a description.
      3. Create in compartment: Select the compartment in which to create the secret.
      4. Vault: Select the vault.
      5. Encryption key: Select the encryption key.
      6. SSL trust store type: Select the trust store type, such as JKS or PKCS12.
      7. SSL trust store location: Enter the trust store location.
      8. SSL trust store password: Enter the trust store password.
      9. SSL key store type: Verify the key store type. It corresponds to the selected trust store type.
      10. SSL key store password: Enter the key store password.
      11. SSL key store location: Enter the key store location.
      12. SSL server certificate distinguished name: Enter the distinguished name of the server certificate.
8. Specify credentials for the connection: Enter the Database user name. If no PDB was specified above, enter the common user name for the CDB and all its PDBs. If an individual PDB was specified, enter the user name for that PDB. Select the database user’s Role. Select the Database user password secret compartment, and then select the Database user password secret that contains the password for the specified user.
   Note
   
   For Government realms, the password for the database user monitoring the Oracle Cloud Database must meet the following Federal Information Processing Standards (FIPS) requirements:

   • Password length must be between 14 to 127 characters.
   • Password must have at least two lowercase, two uppercase, two digits, and two special characters.
   To create a new secret, click Create new password secret.
   Note
   
   In order to create a secret within OCI Vault, the encryption key being used must be set as follows: Click on Key Shape: Algorithm, and select: AES. Advanced Encryption Standard (AES) keys are symmetric keys that you can use to encrypt data at rest.

   Key types, like RSA and ECDSA will not work for encrypting data at rest and are not recommended for Ops Insights operations. For more information see: Creating a Master Encryption Key.

   To change the monitoring user or secret reference, you need to disable the database and then re-enable it (upon re-enable a pop-up displays to allow you to make changes).

   For more information, see Overview of Vault.
9. Management agent: Select the Management agent compartment that contains the Management Agent, and then select the Management agent.
   Note
   
   For Database Management, the Database Management feature set section, when displayed, provides only the Full management option.
10. Click Add databases. The newly added database will appear in the Database fleet administration page.