Add an Exadata Database Service on Cloud@Customer Service System

You can add Exadata systems on the Exadata fleet administration page.

The recommended method of adding Exadata Database Service on Cloud@Customer Service Systems to Ops Insights is via native cloud agent as it gives the full suite of insights, however these can also be added via Enterprise Manager. Adding Exadata Database Service on Cloud@Customer Service Systems via Enterprise Manager is useful for deployments that already have Enterprise Manager targets added into Ops Insights, to add via Enterprise Manager see: Enable an Exadata System Monitored by Enterprise Manager.

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

   The Exadata fleet administration page displays.

3. Click Add Exadata System.
4. Ensure Cloud Infrastructure is selected, and select ExaDB-C@C.
5. Select the Services to enable for the Exadata system. Ops Insights and Database Management can be enabled together.

   If Database Management is selected, specify whether to Enable full Exadata infrastructure monitoring by selecting Yes or No.

6. Click Next to go to the Exadata members section.
7. Select the Exadata Infrastructure compartment, and then select the Exadata Infrastructure to add.
8. Select the VM cluster compartment that contains the VM cluster, and then select the VM cluster.

   You can select either a regular VM cluster or an Autonomous VM cluster. If you select an Autonomous VM cluster, specify the compartments where the Autonomous AI Databases are located.

9. Select the Management agent compartment that contains the Management Agent, and then select the Management agent. A Management Agent is required for both regular and Autonomous VM clusters. This agent is preselected for all databases within the VM cluster.

   If your resource count exceeds the Large configuration, use multiple agents. For detailed information on determining the amount of, and configuring the Management Agents for Ops Insights to work with Exadata Database Service on Cloud@Customer systems see MOS Note: OCI : Observability & Management Support For Exadata Cloud (Article ID PNEWS1338).

   Optionally, click + Another VM cluster to add an additional VM cluster or Autonomous VM cluster. You can include both cluster types in the same onboarding flow.

   Note
   
   For VM clusters a Management Agent local to the database node is not required, network access via Java Database Connectivity (JDBC) from where the agent is located is required.

   If a warning indicates that prerequisites are required for Ops Insights to access databases in the Exadata system, click Complete the prerequisites. Policies created outside Ops Insights might already satisfy these prerequisites.

   Once the Exadata Infrastructure, VM cluster and/or Autonomous VM cluster, and Management Agent have been selected, you have the option of adding member databases now or at a later time. Member databases within the selected cluster appear in the Database members table.

10. To enable a member CDB for Ops Insights, you must set the credentials. Select the database, click the Actions menu, and then select Set connection and credentials.
    1. Set credentials for a VM cluster:
       • Management agent: Exadata Database Service on Cloud@Customer allows you to set a management agent per database.
       • Database: Verify the service name, select the correct protocol (TCP or TCPS), and enter the port.
       • Specify credentials for the connection: Enter the common database user, and password secret.
         Note
         
         The database user should be a common user between the CDB and all PDBs within the CDB. See Creating the Oracle Database Monitoring Credentials for Oracle Cloud Infrastructure Database Management and Ops Insights (Doc ID 2857604.1).
    2. Set credentials for an Autonomous VM cluster:
       • Select the Management agent
       • Select the Database service name connection string. The Protocol and Port will be automatically filled.
       • Specify the named credentials to be used for the connection. These credentials are created by the Agent and do not reside within Ops Insights.
         • TCP: Database credentials
         • TCPS: Database credentials for Autonomous AI Databases (with mTLS)

         For more information, see Deploy Management Agents on Compute Instances.

    Alternatively, you can set the credentials at the cluster level, click Set Credentials for all databases in a VM cluster to display the Set credentials for all databases in VM cluster panel. This is an optional way to set all database credentials in a cluster in a single action, all databases must share the same monitoring credentials to be applied.

11. Enter the required credential information. Optionally you can click on Test credentials to test the connection. To finalize click Set credentials.
12. Click Next to go to the Database system section. In the Database system section:
    • If only Ops Insights is selected, or if both services are selected and only Autonomous VM clusters are selected, no Database Management setup or Cloud Database System discovery is required.
    • If both services are selected and at least one regular VM cluster is selected, complete the following database-discovery steps through Create Cloud Database System.
      Note
      
      Database Management Cloud Database System discovery does not apply to Autonomous VM clusters. Autonomous databases selected for Ops Insights onboarding are not configured for Database Management in this flow.
      1. Click Discover components.

         The wizard first enables Database Management for eligible selected regular databases that have complete credentials. After enablement completes, Cloud Database System discovery starts. Existing Database Management enablement is not repeated.

      2. Wait for database enablement and discovery to complete. If enablement fails, correct the database connection information and retry.
      3. Review the discovered components, which can include databases and PDBs, clusters, ASM, and listeners.
      4. For databases, clusters, and ASM components that require connection information, click Add connection or Change connection. Provide the Management Agent and the required connection details, such as the host, port, service name, protocol, TLS secret when applicable, user name, password secret, and role.

         The wizard might populate some values from the discovery results.

      5. Review the listener components. No Add connection or Change connection action is available for listeners.
      6. Click Create Cloud Database System and wait for the operation to complete.
13. Click Next to go to the Exadata Infrastructure section. In the Exadata Infrastructure section:
    • If only Ops Insights is selected, no Database Management Exadata infrastructure discovery is required.
    • If both services are selected, and for Database Management, if Enable full Exadata infrastructure monitoring is set to Yes:
      1. Click Discover Exadata infrastructure.
      2. Select the storage servers to monitor.
      3. Configure a connector for each selected storage server.
      4. Create or update the Database Management Cloud Exadata Infrastructure, and wait for the operation to complete.

      If both services are selected, but if Enable full Exadata infrastructure monitoring is set to No, no Database Management Exadata infrastructure discovery is required.

14. Click Next to go to the Review section and review the configuration.
15. Click Add Exadata System.

As noted earlier, if you did not enable all member databases while adding the Exadata system to Ops Insights, you can add them on the Exadata details page by clicking Add members. The newly added system will appear in the Exadata fleet administration page.