Add a Cloud Service Database

With a private endpoint defined, you are ready to add a database that uses that endpoint. You can add databases from the Private endpoint details page or 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 (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.

   Note
   
   If deprecated policy statements are detected, Policy Advisor will display a banner requiring a policy update to the new CRISP format, to update click Update prerequisites polices. For information on deprecated policies, see Service Principal Policy Removal.
3. Click Add databases.
4. Under Telemetry, select Cloud Infrastructure.
5. In the Database type field, select the appropriate database type.
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. Enter the required database selection information:
   1. Depending on the database type, select the required resource:
      • For Bare metal, VM, select the Database system compartment and Database system.
      • For Exadata Database Service on Dedicated Infrastructure, select the VM cluster compartment and 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 container database, 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

      For more information, see Enable Diagnostics & Management for Oracle Cloud Databases.

   5. Service name: If no pluggable database was specified above, enter the service name corresponding to the container database (CDB). If one was specified, enter the service name corresponding to the specified pluggable database.
   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 compartment which contains the secret and the secret or click Create new wallet secret to create a new secret, the Create database wallet secret panel appears.
      In the Create database wallet secret panel, 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.
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 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 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. Private endpoint information: Select the Ops Insights private endpoint compartment, and then select an Ops Insights private endpoint that has network access to the database via a VCN.

   For information about creating Ops Insights private endpoints, see Create a Private Endpoint.

   If Database Management is also selected, select the Database Management private endpoint compartment, and then select the Database Management private endpoint that has network access to the database. If the required ingress and egress security rules have not been configured, click Add network security rule. For information about Database Management private endpoint requirements and adding security rules, see Enable Diagnostics & Management for Oracle Cloud Databases.

10. If Database Management is selected under Services, select a management option in the Database Management feature set section, if displayed.

    For information on the management options, see About Management Options.

11. Click Add databases. The newly added database will appear in the Database fleet administration page as well as the Private endpoint details page.