Discover RDS Database on OCI Database Management

This article describes the steps required to discover the RDS database on OCI database management.

There are two types of databases available with (RDS):

• The first one is Amazon Relational Database Service for Oracle

  Amazon RDS for Oracle is a cloud-based database service offered by Amazon Web Services (AWS). It allows users to set up, operate, and scale Oracle relational databases in the cloud without the need to manage the underlying infrastructure. This is a non-container database.

• Amazon Relational Database Service Custom

  Amazon RDS Custom a managed database service for legacy, custom, and packaged applications that require access to the underlying OS and DB environment. Amazon RDS Custom is now available for Oracle Database. Amazon RDS Custom for Oracle automates setup, operation, and scaling of databases in the cloud while granting access to the database and underlying operating system to configure settings, install patches, and enable native features to meet the dependent application's requirements. This can be a container database (CDB) with pluggable databases (PDB).

You can discover both the databases using OCI Database Management service, the first one as non-container database and the second one as container database.

To discover these databases, first you need to create database connector handles to discover the databases in an OCI external database.

Create a Non-Container Database Handle

First, you need to create a non-container database handle. Used this procedure:

1. Open the navigation menu and select Oracle Database then External Database.
2. Under External databases, select Container databases.
3. Select your Compartment. A list of external databases appears.
4. Click Register external container database. The Register an external container database dialog opens.
5. Choose a compartment. By default, the database is created in your current compartment.
6. In Database display name, provide a user-friendly name to help you easily identify the resource.
7. Click Show advanced options. If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
8. Click Register.

Create a Container Database Handle

Next, use this procedure to create a container database handle.

1. Open the navigation menu. Select Oracle Database then External Database.
2. Under External databases, select Container databases.
3. Select your Compartment. A list of external databases appears.
4. Click Register external container database. The Register an external container database dialog opens.
5. Choose a compartment: By default, the database is created in your current compartment.
6. In Database display name, provide a user-friendly name to help you easily identify the resource.
7. Click Show advanced options to specify the options for the database. If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
8. Click Register.

Similarly create the Pluggable database handle to connect the PDBs on a container database. Navigate to the Menu, then Oracle Database and select External Database. Under External Databases, select Pluggable Databases and follow the steps described above.

Connect to the Container External Database

Use this procedure to create a connection to an external container database.

1. Open the navigation menu. Select Oracle Database then External Database.
2. Under External databases, select Container databases.
3. Select your Compartment. A list of external databases appears.
4. In the list of external databases, click the name of the database for which you want to create the connection. Details of the external database you selected appear.
5. Click Connect to external container database. The Connect to an external container database dialog opens.
6. In Connector display name, provide a user-friendly name to help you easily identify the resource.
7. Select a connector type, provide a connector type for the external database.
   For MACS, create an OCI Management Agent Cloud Service (MACS) connector to access your external database. You must configure the agent prior to connecting your external database. Select this option if you are using TCPS.
8. In Connector agent ID, provide a connector agent ID. This is required only if you select MACS.
9. In External site ID, provide an external site ID. This is required only if you select external site.
10. Specify a connection string information for the connection.
11. In DNS hostname or SCAN name, provide virtual IP (VIP) address or single client access name (SCAN) for the database on your premises that you are connecting to the OCI.
12. In Port, provide the port being used by the database outside OCI for database connections.
13. In Service, provide the service name being used by the database outside OCI for database connections.
14. In Protocol, provide the protocol being used by the database outside OCI for database connections. You can select from either TCP or TCPS.
15. If you selected TCPS protocol, select between the following options:
    • Use existing secret
    • Create a new secret

    When you select Use existing secret, provide a Database user password secret in your compartment. When you click Create a new secret, the Create TLS Secret windows opens. Provide the following details, and then click Create TLS secret.

    • Secret name: Name for the secret you are creating.
    • Description: (Optional) Description for the secret.
    • Choose a compartment: The compartment where the secret must be stored.
    • Vault in your compartment: Vault in your compartment where the secret is stored.
    • Encryption key in your compartment: Encryption key in your compartment where the secret must be stored. SSL
    • Trust Store Type: Type of the SSL trust store. Available options are PKCS12 and JKS. BCFKS is the only available option in US government regions.
    • SSL Trust Store Location: Fully qualified path of the SSL trust store on the agent host.
    • SSL Trust Store Password: password of the SSL trust store.
    • SSL Key Store Type: (Read-only) Type of the key store. It is automatically chosen to be the same as the SSL trust store type.
    • SSL Key Store Location: Fully qualified path of the key store on the agent host.
    • SSL Key Store Password: password of the key store.
    • SSL Server Certificate Distinguished Name: Unique name for the SSL server certificate.
16. Specify database connection credentials for the connection.
17. In Username provide the user name for the database credentials to be used by this connection.
18. In Password, provide the password for the database credentials to be used by this connection.
19. In Credential name prefix: This string is the first part of the full credential name. Your prefix is prepended to a system-generated Credential name prefix to create the full credential name.
20. In Credential name: (Read-only) enter the connection's credential name.
21. In Role, provide the role for the database credentials to be used by this connection. You can select between NORMAL and SYSDBA.
22. Click Show advanced options to specify options for the database. If you have permissions to create a resource, then you also have permissions to apply a free-form Tag to that resource. To apply a defined tag, you must have permissions to use the tag namespace. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator. You can fine more information in "Resource Tags" (see "Explore More").
23. Click Connect to external container database.
24. Now, repeat the preceding steps to create the Pluggable database handle to connect the PDBs on a container database. To get started:
    Open the navigation menu. Select Oracle Database then External Database. Under External databases, select Pluggable databases, then enter the details similar to the Container database and select Connect to external pluggable database.

Enable OCI Database Management

This topic describes two ways you can enable OCI Database Management. You can also use either of these procedures to enable Non-Container and Pluggable Databases (PDBs).

1. Open Observability & Management menu and select Database Management.
2. On the left pane, select a compartment from the Compartment drop-down list and External in the Deployment type drop-down list.
3. The external databases in the compartment are listed on the Managed databases page. These external databases could have been registered either in the Oracle Cloud Infrastructure External Database service or in Database Management.
4. In the Management status column, click Enable Database Management.
5. In the Enable Database Management panel, review the billing information, select an External Database connector from the drop-down list, select a license type, and click Enable.
6. You can verify if Database Management is successfully enabled on the following pages:
   • Database Management Managed databases page: On the left pane, select the compartment in which the External Database resides and select External in the Deployment type drop-down list. After Database Management is enabled, Enabled - <license type> appears in the Management status column. You can click the name of the database to go to the Managed database details page and monitor and manage the External Database by using Database Management.
   • External <database type> details page of the External Database service: On the left pane under Resources, click Metrics and check if database metrics are displayed.

An alternate way to enable Database Management is to enable Database Management for External Databases (CDB/PDB and Non-Container) and then:

1. Open the navigation menu and select Oracle Database. Under Oracle Database, click External Databases.
2. On the left pane, select the Container Databases.
3. Click the Container Database where you want OCI Database Management enabled.
4. On the container database's home page, note the section labeled Associated Services.
5. Under the Associated Services, click Enable Database Management.
6. Choose the database container and the associated billing information and click Enable.

You can us this same procedure to enable non-CDB and PDBs. To get started, on the External Database menu, navigate to the Pluggable databases, then select the pluggable database and enable database management under Associated services. Then follow the steps above to enable the databases.

Enable OCI Ops Insights for Databases

OCI Ops Insights service can be enabled for the PDBs only. To enable OCI Ops Insights for the PDBs discovered externally, use this procedure.

1. Open the navigation menu, click Oracle Database and, under Oracle Database, click External Database.
2. On the left pane, select the Pluggable Databases.
3. Click the pluggable database where you want the Ops Insights enabled.
4. On the pluggable database home page, note the section, Associated Services.
5. Under the Associated Services, click Enable under Ops Insights.
6. Choose the Database Container and click Enable.

Enable OCI Ops Insights for Database Hosts

OCI Ops Insights service can be enabled for the hosts that runs the databases on AWS. To enable the hosts for OCI Ops Insights capacity planning, use this procedure.

1. Open the OCI navigation menu and select Observability and Management.
2. Select Ops Insights then Administration.
3. On the Administration menu, select Host Fleet.
4. Click Add Hosts then choose the Telemetry as OCI Management Agent.
5. Choose the compartment, then select the AWS hosts to enable Ops Insights.
6. Select the destination compartment in case of the Ops Insights in different compartment.
7. To add the hosts to Ops Insights, click Add Hosts.

Enable OCI Stack Monitoring for External Database

OCI Stack Monitoring service can be enabled for all the discovered CDB/PDB and non-CDB databases. To enable stack monitoring, use this procedure.

1. Open the navigation menu and select Oracle Database.
2. Under Oracle Database, click External Database.
3. On the left pane, select the Container Databases.
4. Click the container database where you want Stack Monitoring enabled.
5. On the container database home page, note the section Associated Services.
6. Under Associated Services, under Stack Monitoring, click Enable.
7. Choose the database connector and click Enable.

Note:

There are other ways to enable OCI Stack Monitoring for the external databases. See "Resource Discovery and Promotion" in the OCI documentation for more details on the various methods by which you can enable a stack monitoring service (see "Explore More").

Similarly, you can use the same steps to enable OCI Stack Monitoring for PDBs and non-CDB databases. Open the navigation menu and select Oracle Database. Under Oracle Database, click External Database. On the left pane, select the Pluggable Databases. Then follow the steps above.

Enable OCI Stack Monitoring for Hosts

To enable OCI Stack Monitoring for the hosts that host the AWS databases, use this procedure.

1. Open OCI navigation menu and click Observability and Management.
2. Select Application Performance Monitoring then Stack Monitoring.
3. Under the Stack Monitoring Resources left menu, select Resource Discovery.
4. Select Discover New Resource the choose the resource type as host.
5. Select the agent and license type then click Discover New Resource.
   Alternatively, navigate to Promote to full monitoring on the Stack Monitoring Left pane, if you see the hosts on the lists, then click Promote to enable the host for full monitoring.

Once all the services are enabled, then navigate to each service and configure the respective home pages, then configure the dashboards, alerts and notifications for each service. For more deetails, refger to Overview of Notifications and the Management Dashboard (see "Explore More").