Connect to a Database From a Private Endpoint-Enabled Instance

If your Visual Builder instance was provisioned as a private endpoint, you might need to do some additional configuration when switching to an Oracle database instance.

Note:

If the private endpoint-enabled VB instance and the database service are in different virtual cloud networks (VCNs), you will need to create private views inside the VCN private resolver so that both VCNs can resolve hosts and endpoints in the other VCN. For more information, see About the DNS Domains and Hostnames.

To use an Oracle database with your private endpoint-enabled VB instance:

  1. Get the connection details for the database instance.

    If you are not using an ATP wallet, you need to use JDBC to connect to your Oracle DB instance, and you will need to use the quick URL connection string, which contains only the database's host name, as the URL. You cannot use the service's long URL connection string, which contains both the private IP address and host name.

  2. Add the appropriate database port to your private endpoint-enabled VB instance's security list or NSG rules.

    Typically the port is 1521, but you need to confirm the correct port for your database instance.

    For more on configuring rules, see Configure Private Endpoint Advanced Network Options .

  3. Switch to the Oracle DB instance.

If you have problems connecting to the database, you can try to debug the problem by creating a compute instance in the private subnet, and then connecting to the database from the compute instance using the database's host name. If you can successfully connect to the database from a compute instance residing in the same private subnet, then connecting to the database from the Visual Builder instance will also work.