You can add Exadata Cloud@Customer databases from 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 (Doc ID 2942938.1). It is strongly recommended the script be run every 6 months or if any databases are missing the storage or tablespace data.

1. From the Ops Insights main menu, click Administration and then Database Fleet.
2. Click Add Databases. The Add Databases to Ops Insights dialog displays.
   
   
   
   
3. For Telemetry select Cloud Infrastructure.
4. Under Choose a cloud database type, select Bare metal, VM and Exadata. The Select Database region displays.
5. Enter the required database selection information:
   1. Database Type: Choose either Bare Metal, Virtual Machine or ExaDB-D. For each database type, there are different resources that can be specified:
      1. For Bare metal, VM you can only add database systems
      2. For ExaDB-D, you can only add VM Clusters
   2. Database system: Select a database system (Bare Metal, VM Clusters for ExaDB-D) from the current compartment. If needed, you can change compartments by clicking on (Change compartment).
   3. Database Home: Select a database home (system or cluster). All database homes in the database system are available in the drop-down selector.
   4. Database: Select a database from the database home. Databases are identified as either container or non-container.
      Note
      
      When PDBs are added or removed from the DB System or VM Cluster, they will automatically be enabled or disabled:

      • When performing disable, you should simply select the CDB and disable that target alone. That will disable all the PDBs as well.
      • When performing a delete, you should simply select the CDB and disable that target alone. That will disable all the PDBs as well.
      • If you previously disabled the CDB (and thus all the PDBs) and you want to re-enable Ops Insights, you should do so just on the CDB resource.
   5. Service Name: Enter the service name corresponding to the container database (CDB).
   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. Database Wallet Secret (only for TCPS): When using a TCPS connection protocol a database wallet secret is required. Select the corresponding secret from the drop down list or click Create new wallet secret to create a new secret, the Create database wallet secret window appears.
      In the Create database wallet secret enter the following information:

      • Name: Wallet secret name.
      • Description (optional): Description for the wallet.
      • Create in compartment: Database compartment where the wallet will be used.
      • Vault: Vault within the compartment where the wallet will be stored.
      • Encryption key: Encryption key to be used, select from drop down menu.
      • Wallet format:
        • For Java key store (JKS files) wallets the following is additionally required:
          • Key store password: Enter the key store password for the Java key store wallet..
          • Key store content: Drag the JKS file into the Ops Insights UI from a local machine.
          • Trust store password: Enter the Trust store password required for the Java key store wallet.
          • Trust store content: Drag the Trust score JKS file into the Ops Insights UI from a local machine.
        • For PKCS#12 (P12 files) wallets the following is additionally required:
          • Wallet password: Enter the required PKCD#12 wallet password.
          • PKCS#12 wallet content: Drag the P12 file into the Ops Insights UI from a local machine.
      • Certificate DN: Enter the certificate chain to be used.
6. Specify credentials for the connection: Enter the Common database user and the Database user password secret for the selected compartment.
   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 .
7. Private endpoint informationSelect a Private endpoint that has network access to this database via a VCN.

   To create a new private endpoint, click Create New Endpoint to access the Private Endpoint Administration page. For more information about creating private endpoints, see Create a Private Endpoint.

8. Click Add Databases. The newly added database will appear in the Database Fleet Administration page as well as the Private Endpoint Details page.