Skip to main content
The Oracle connector supports standard Oracle databases and Oracle Autonomous Database (which requires TLS / TCPS and a wallet certificate). The form is split into three sections — Connection, Credentials, and Wallet SSO Certificate.

​
What you’ll need

  • A reachable Oracle host and port (default 1521).
  • A service name (not SID).
  • A user with SELECT on the schemas/tables you want exposed.
  • For Autonomous Database, the client credentials wallet (Wallet_<dbname>.zip) downloaded from the OCI console. See Download client credentials.

​
Connection

The Connection section has a toggle at the top — describe the connection either as host/port/service, or as a single EZConnect-style string. The two views stay in sync: filling host/port/service builds the equivalent string, and pasting a string parses it back into the discrete fields when possible. EZConnect syntax is documented under Easy Connect Naming Method in the Oracle Net Services Administrator’s Guide.

​
Host & service name (default)

​
Connection string

​
Credentials

​
Wallet SSO Certificate (optional)

Required for Oracle Autonomous Database and any deployment that uses a wallet for TLS. You can either upload the wallet file or paste its contents. To find the wallet, see Download client credentials — the file you want is cwallet.sso from the unzipped wallet bundle. The certificate is stored as a secret. Summation base64-encodes it for you — you don’t need to encode it by hand.

​
Adding datasets

Source references quote the schema and table names:

​
Common problems