How to Create and Connect to an Oracle Connection in VDM

Create an Oracle Connection Profile in VDM to access Oracle data for Views and reports. The steps below cover the VDM wizard and use an Oracle Autonomous Database connection string as the example.

Trouble viewing images? Right-click an image and select Open image in new tab to view it at full size.

Before You Begin

• Have an Oracle database username and password with access to the required tables and views.
• Obtain the correct data source connection information from your Oracle administrator.
• Confirm that the VDM computer can reach the database endpoint through the required network path.
• For Autonomous Database, confirm whether the connection uses TLS or mutual TLS (mTLS).
• Create the profile on the computer where it will be used.

The retained screenshots show the original workflow. Oracle’s current documentation uses the name Autonomous AI Database, and console labels or layout may differ.

Oracle Connection Requirements

Choose VDM’s Oracle connection type for this workflow; it does not use an ODBC DSN.

Wallet-free Autonomous Database connections are conditional. Oracle documents wallet-free TLS connections for supported ODP.NET managed and Core clients when TLS is allowed on the database. mTLS requires client credentials and wallet configuration. See Oracle’s ODP.NET connection documentation and Autonomous Database connection overview.

This guide describes the TLS connection-string workflow shown in the screenshots. If your database requires mTLS or another authentication method, ask BridgeWorks Support to confirm the supported configuration for your VDM version before proceeding. Oracle’s client documentation does not establish which provider version your VDM installation includes.

Have your Oracle administrator confirm the approved TLS and network settings. Do not change the database’s authentication policy simply to match this example. Oracle documents the available settings in Update Network Options to Allow TLS or Require Only mTLS.

Create the Oracle Connection Profile

Step 1: Open VDM

Launch VDM on the computer where you will use the Oracle connection.

Step 2: Start the Connection Wizard

Select Database > New on the ribbon.

Step 3: Select Oracle

Choose Oracle as the connection type. Enable Prefix TO/Schema Name as shown so queries include the owner or schema prefix. Confirm any different requirements with your Oracle administrator.

Step 4: Enter Database Credentials

Enter the Oracle database Username and Password provided for reporting access. Use database credentials, rather than assuming your Oracle Cloud console sign-in is also a database login.

Step 5: Enter the Data Source

For Oracle Autonomous Database:

1. Open the database’s details page in the Oracle Cloud Infrastructure console.
2. Select Database connection.
3. For the wallet-free workflow, select TLS under TLS authentication. If TLS is unavailable, consult your Oracle administrator.
4. Select the appropriate service connection string and use Copy. If access-type options are shown, choose the endpoint reachable from your VDM computer.
5. Paste the complete connection descriptor into VDM’s Data Source field.

Copy the connection string itself, not only its TNS name or a JDBC URL. Preserve the descriptor’s host, port, service name, and security settings. Oracle’s current procedure is documented in View TNS Names and Connection Strings.

For other Oracle databases: Use the data source descriptor supplied by your Oracle administrator. The Autonomous Database console steps do not apply to every Oracle deployment.

Step 6: Test the Connection

Select Test Connection. If the test succeeds, acknowledge the confirmation by selecting OK and continue through the wizard.

If the test fails, check the database credentials, complete data source descriptor, endpoint access, and TLS or wallet requirements before testing again.

Step 7: Select Owners or Schemas

Select the owners or schemas you want to browse in VDM.

This selection controls which schemas are included in the profile; it does not grant database permissions. Your Oracle account must already have access to the required objects.

Step 8: Save the Profile

Enter a clear Connection Name, such as Oracle_ADB_Prod, and select Save.

Step 9: Load and Open the Connection

Select Load All on the Database ribbon or in the lower-left corner of VDM. Locate the saved Oracle profile in Tables and Fields and open it.

Verify the Connection

Confirm that the connection is active, expand the selected schemas, and check that the expected tables and fields are available. Run a View and review the returned data.

For connection indicators, see How to Open a Database Connection in VDM.

Troubleshooting

• Connection fails: Check the database account, password, host, service name, and copied descriptor.
• Network or timeout error: Have your administrator check endpoint reachability, firewall rules, and Oracle network access restrictions.
• TLS or wallet error: Confirm the database authentication mode and VDM compatibility. Copying a connection string does not remove mTLS wallet requirements.
• Missing tables: Review the selected owners or schemas and ask your Oracle administrator to verify object permissions.

Need Help?

Contact support@bridgeworksllc.com with your VDM version, Oracle deployment type, TLS or mTLS configuration, and error message. Do not include passwords or wallet files.