Oracle (ORDS)
Connect TableR to Oracle Database over Oracle REST Data Services (ORDS) with the oracle-driver plugin: connection fields, schema alias, SSL/TLS, verifying the connection, and troubleshooting.
Oracle is reached through Oracle REST Data Services (ORDS) over HTTP/HTTPS — the connection is provided by the oracle-driver plugin (install it from the plugins page). Provide the ORDS host, a schema-enabled user, and that user's password.
Overview
TableR connects to Oracle through the ORDS SQL endpoint at {host}:{port}/{base path}/{schema}/_/sql — it does not use the Oracle wire protocol (1521) or a service name/SID. Authentication is HTTP Basic over the ORDS endpoint, so HTTPS is strongly recommended for any remote database. The {schema} segment is an ORDS schema alias, not the service name.
- ORDS endpoint — the database is reached at http(s)://host:port/ords, not over the 1521 wire protocol.
- Plugin-gated — the Oracle card appears once the oracle-driver plugin is installed.
- Basic auth — the ORDS schema-enabled username and password authenticate every request; keep them in the keyring.
- Read-only — the oracle-driver is a read-only driver; browsing and SELECT are supported.
Before you start
- The oracle-driver plugin installed (Plugins → Oracle (ORDS) → Install).
- Oracle REST Data Services (ORDS) running and schema-enabled for your user.
- The ORDS host and port (default 8080 for HTTP, 443 for HTTPS).
- An ORDS schema-enabled username and its password.
- Optionally, the ORDS schema alias and base path when they differ from the defaults.
Connection fields
These fields match TableR's Oracle (ORDS) connection form. The password is stored in the operating system keyring, never in plain configuration files.
| Field | Required | Default | Notes |
|---|---|---|---|
| Host | Yes | — | The ORDS host — the machine running ORDS, not the database listener. |
| Port | No | 8080 / 443 | ORDS HTTP port (default 8080); 443 when SSL/TLS is enabled. |
| Username | Yes | — | An ORDS schema-enabled database user; authenticates via HTTP Basic. |
| Password | Yes | — | The ORDS user's password; stored in the OS keyring. |
| Schema | No | — | ORDS schema alias (the Database field, or ords_schema); defaults to the username. |
| Base path | No | ords | The ORDS base path segment (ords_base_path) when ORDS is not mapped at /ords. |
| SSL/TLS | No | Off | Enable for HTTPS; required for any remote ORDS endpoint. |
Connect with the form
- 1Install the Oracle plugin
Open Plugins, find Oracle (ORDS), and install the oracle-driver plugin.
- 2Choose Oracle (ORDS)
Open the launcher and pick the Oracle (ORDS) card.
- 3Enter the ORDS host and port
Use your ORDS host and port (8080 for HTTP, 443 for HTTPS).
- 4Add credentials
Type the ORDS schema-enabled username and password; the password is saved to the keyring.
- 5Set the schema (optional)
Use the Database field for the ORDS schema alias; it defaults to the username.
- 6Enable SSL/TLS for remote
Turn on SSL/TLS to reach ORDS over HTTPS on port 443.
- 7Save and connect
Save the profile so it reappears in the launcher, then connect.
SSL/TLS
The Oracle plugin authenticates with HTTP Basic, so credentials travel in every request. Always enable SSL/TLS so the ORDS endpoint is HTTPS — only skip it for a local, trusted ORDS install.
- Off — plain HTTP to the ORDS endpoint (local development only).
- On — HTTPS to the ORDS endpoint on port 443.
- Enable it for any remote or shared database.
Verify the connection
Once connected, open a query tab and run SQL against the schema:
SELECT 1 FROM DUAL;
SELECT banner FROM v$version;If both statements return rows, the ORDS endpoint, credentials, and schema alias are all correct.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Oracle card missing | The oracle-driver plugin is not installed. | Open Plugins and install the Oracle (ORDS) driver, then retry. |
| Oracle ORDS username/password is required | The username or password field is empty. | ORDS uses HTTP Basic auth — both fields are required. |
| 404 / path not found | Wrong ORDS base path or schema alias. | Re-check ords_base_path (default ords) and the schema alias; it must be schema-enabled. |
| 401 / authentication failed | Wrong username or password, or the user is not schema-enabled. | Re-check the ORDS credentials and confirm the user is REST-enabled in ORDS. |
| Connection refused | ORDS not running, wrong host/port, or a firewall. | Confirm ORDS is up and reachable on the configured port. |