Skip to main content

​
Oracle Database Connections

TablePro supports Oracle Database 11.1 and later. It speaks the Oracle TNS wire protocol directly in Swift, so no Oracle Instant Client or other external library is required. This covers Oracle Database instances running on-premises, in Docker, or Oracle Cloud.
Oracle 10g and earlier are not supported: they use the older O3LOGON handshake that the pure-Swift driver does not implement.
Servers behind a RAC SCAN listener, shared server, or a load balancer are supported: TablePro follows the listener’s redirect to the instance that serves the session. Servers that require Native Network Encryption (SQLNET.ENCRYPTION_SERVER or SQLNET.CRYPTO_CHECKSUM_SERVER set to REQUIRED) are also supported: TablePro offers AES encryption with a SHA crypto-checksum to every server and the server turns it on when required, the same as SQL Developer and DBeaver. There is no option to configure.

​
Install Plugin

The Oracle driver is available as a downloadable plugin. When you select Oracle in the connection form, TablePro will prompt you to install it automatically. You can also install it manually:
  1. Open Settings > Plugins > Browse
  2. Find Oracle Driver and click Install
  3. The plugin downloads and loads immediately, no restart needed

​
Connection Settings

Enter host, port, username, password, and service name, then click Save & Connect.
Oracle connection form with Connection Type and Service Name fields

Oracle connection form

​
Example Configurations

Local (Oracle XE): host localhost:1521, user system, service XEPDB1 Docker: gvenzl/oracle-xe:21-slim image, same config as local Remote: Standard host/port/credentials, service name from DBA Oracle Cloud (ADB): Copy host, port, and service name (format mydb_tp) from the TLS connection string in the Oracle Cloud Console, then set SSL mode to Required (or Verify CA with the CA certificate). No wallet needed: the connection uses one-way TLS, and the driver does not read Oracle wallet files. SSL/TLS: OracleNIO has no TLS fallback. Preferred connects in plain TCP (the SSL pane shows a warning). Use Required for TCPS, Verify CA with a CA certificate path for strict validation. See SSL/TLS for details.

​
Connection URL

See Connection URL Reference for all parameters.

​
Features

Schema Selection: Each user is a schema. The sidebar lists every schema and loads a schema’s tables when you expand it. Switch the active schema with Cmd+K or the Schema toolbar button. Table Info: Structure (columns, types, nullability, primary keys), indexes, foreign keys, and CREATE TABLE DDL. Query Editor: SQL and PL/SQL (anonymous blocks). Pagination uses OFFSET/FETCH syntax:
Schema Editing: ALTER TABLE with double quotes for case-sensitive names. Supports ADD, RENAME COLUMN, MODIFY, DROP, CREATE INDEX. Authentication: Username/password only (no OS auth or wallet). Create user: CREATE USER app_user IDENTIFIED BY "Password1!"; GRANT CREATE SESSION, SELECT ANY TABLE TO app_user;

​
Auth Compatibility

TablePro authenticates via OracleNIO, a pure-Swift implementation of the Oracle TNS wire protocol (no Oracle Instant Client needed). 10G hash is supported for compatibility with legacy environments. It uses DES-based hashing without modern salting and is deprecated by Oracle. We recommend rotating affected accounts under modern auth so password_versions contains only 11G or 12C:
If the connection fails with “Unsupported Password Verifier”, check password_versions first. “Server Version Not Supported” means the database is older than 11.1 (10g or earlier), which the driver cannot connect to.

​
Column Type Support

Columns with types not yet supported render as <unsupported: type> rather than crashing or corrupting data. Report unsupported types via GitHub Issues.

​
Troubleshooting

Connection refused: Check listener running (lsnrctl status), verify port 1521 open, if Docker check docker start oracle-xe Invalid service name: Verify service exists: SELECT value FROM v$parameter WHERE name = 'service_names'; List services: lsnrctl services Connection dropped during handshake: The server closed the connection mid-login. The error dialog shows the handshake phase it stopped at (for example advancedNegotiation, dataTypeNegotiation, or authentication). Check for a firewall, VPN, or proxy that resets traffic, and confirm the host and port reach the listener directly. Native network encryption not completed: The server requires native network encryption and the negotiation did not finish. The server likely requires an encryption or checksum algorithm the driver does not support; the error dialog shows the reason. File an issue with your Oracle version and that reason. For encryption in transit you can also use TLS by setting an SSL mode in the SSL settings. Login handshake timed out: The TCP connection is accepted but login never finishes, so the connect stops after 30 seconds instead of waiting for the server to reset. Check for a firewall, VPN, or proxy that stalls traffic after the TCP handshake, and confirm the host and port reach the listener directly. Limitations: Username/password only, BFILE shows locator metadata only (content fetch via DBMS_LOB not supported), PL/SQL limited to anonymous blocks.