Databases Already Registered with Ops Insights

Figure 10-2 Adding an Ops Insights Registered Database

1. Make sure the check mark for Ops Insights registered databases is selected. Select the Compartment where the database resides, and Select the available database to add. Click Next.
2. Enter a name for the AWR Source, it is populated by default with the database name, and click on Complete the Prerequisites to view the required policies and definitions to be applied.
   • Autonomous - Shared databases will use policy: allow dynamic-group OPSI_AWR_Hub_Dynamic_Group to manage opsi-awr-hub-sources in tenancy.
   • External registered databases will use: allow group <User Group> to use opsi-awr-hub-sources in tenancy.
3. On the emerging pop-up click Next to apply the required policies and definitions. Click Close once the policies and definitions have been successfully applied.
4. Click on Add AWR Source, copy the displayed PL/SQL, log into the database with administrator privileges, and execute the PL/SQL to register the database to the AWR Hub. Click Close once the PL/SQL has been executed in the database.
5. The AWR source has now been added.

Autonomous - Dedicated databases

Figure 10-3 Adding and Autonomous Dedicated Database

1. Uncheck the The database is registered with Ops Insights check mark.
2. Under Type select Autonomous - Dedicated, the compartment where the database resides, and select the available database to add. Click Next.
3. Enter a name for the AWR Source, it is populated by default with the database name. Click on Complete the Prerequisites to view the required policies and definitions. Autonomous - Dedicated databases will use the allow group <User Group> to use opsi-awr-hub-sources in tenancy policy.
4. Click Next to apply the required policies and definitions. Click Close once the policies and definitions have been successfully applied.
5. Click on Add AWR Source, copy the displayed PL/SQL, log into the database with administrator privileges, and execute the PL/SQL to register the database to the AWR Hub. Click Close once the PL/SQL has been executed in the database.
6. The AWR source has now been added.

External Databases

Figure 10-4 Adding an External Database

1. Uncheck the The database is registered with Ops Insights check mark.
2. Under Type select External - Not registered with External Database Service, the compartment where the database resides and select the database version, and click Next.
3. Enter a name for the AWR Source and click on AWR Source.
4. Follow the patching steps listed in the pop up. Once complete click Next.
5. Copy the displayed PL/SQL, log into the database with administrator privileges, and execute the PL/SQL to register the database to the AWR Hub. Click Close once the PL/SQL has been executed in the database.
6. The AWR source has now been added.

Additional Operations

You can perform additional operations on registered AWR Sources by clicking on the vertical ellipses menu on the right hand side of each AWR Source database:

Figure 10-5 Additional Operations for AWR Sources

• Patch database information: Will display the patches required for non-registered external databases in order to be added into the AWR Hub.
• Register database information: Displays the required PL/SQL code required to register a database.
• Unregister database information: Displays the required PL/SQL code required to remove a database.
• Start accepting snapshots: Selecting this will enable snapshot collection.
• Stop accepting snapshots: Selecting this will disable snapshot collection.
• Delete: Deletes the AWR source from the AWR hub.