Skip to main content
Connect your Oracle database to Basedash to visualize and analyze your enterprise data. Basedash connects directly and queries your data in place. The easiest way to connect is by using a connection string (URI). In Basedash, press Command + K and paste your connection string to start the connection flow immediately. Example:

​
Manual connection details

If you prefer to enter credentials manually, use the following details:
  1. From your Basedash dashboard, click “Add Data Source”
  2. Select “Oracle” as your database type
  3. Enter your connection details:
    • Host (e.g., your-db.host.com). You can also paste a full connect descriptor, such as (DESCRIPTION=(ADDRESS=...)(CONNECT_DATA=...))
    • Port (default: 1521)
    • Database name: the Oracle service name (e.g., orclpdb1)
    • Username
    • Password
    • SSL (enable to connect over TCPS)
  4. Click “Test Connection” to verify
  5. Save your connection

​
SSH tunnel

For enhanced security when your database is in a private network:
  1. Follow the manual connection steps above
  2. Enable “Connect via SSH” option
  3. Add our IP (24.199.77.73) to your allowlist
  4. Provide SSH connection details:
    • SSH host
    • SSH username
    • Set “Authentication method” to “Private key” (recommended) and upload your SSH private key. Password authentication is also supported.
  5. Test and save the connection

​
Required permissions

Create a dedicated user for Basedash with read access to the schemas you want to analyze:
Repeat the SELECT grant for each table or view Basedash should see, or use a role that bundles them.

​
Best practices

  • Use a read-only user for Basedash
  • Enable SSL (TCPS) for secure connections
  • Consider using an SSH tunnel for databases in private networks
  • Regularly rotate database credentials

​
Troubleshooting

  • Use the service name, not the SID, in the database name field
  • Verify firewall and listener settings allow connections from the Basedash IP (24.199.77.73)
  • If SSL fails, confirm your listener accepts TCPS connections on the port you entered
  • Confirm the user has CREATE SESSION and SELECT on the tables you expect to see

​
Next steps: Add custom context

You can add custom context to help the AI better understand your data structure and business logic. Consider adding context at the database or schema level if you notice the AI struggling to locate or understand specific data.

​
When to add context

  • Unclear naming conventions: If table or column names don’t clearly indicate their purpose
  • Business-specific terminology: When your data uses internal abbreviations or custom terms
  • Large enterprise schemas: When the AI needs help finding the right tables among many
For detailed guidance, see our custom context documentation.