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. Under Exadata Infrastructure in <compartment name>, select the desired Exadata infrastructure from the drop-down menu. You can change the compartment if necessary. Changing the compartment will query that compartment for valid Exadata Infrastructures.
6. Select the VM cluster and the default Management Agent (this agent will be preselected for all the databases within a VM cluster) from their respective drop-down menus to change the default value.

   You can select either a regular VM cluster or an Autonomous VM cluster. When selecting an Autonomous VM cluster, the default Management Agent section will be grayed out, and you will need to enter the compartments where the Autonomous AI Databases are located.

   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, you may add additional VM clusters or Autonomous VM clusters by clicking + Another VM cluster, both types of clusters can be added simultaneously.

   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.

   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 Members table.

   IMPORTANT: At least one Container Database must be added (if one was not previously on-boarded). It is required to pull the Exadata metrics.

7. To enable a member Container Database for Ops Insights, you must set the credentials. Select the database you wish to set the database credentials for, click the Actions menu and select Set 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 Container Database and all Pluggable Databases within the Container Database. 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.
        • For TLS (TCP) use PENDING named credential
        • For Mutual TLS (TCPS) use PENDING named credential

        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.

8. Enter the required credential information: Optionally you can click on Test credentials to test the connection. To finalize click Set credentials.
9. 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.