Read from Oracle Database (12c and later) using service name or SID connections
## Overview The Oracle Database connector enables DeltaForge to read data from Oracle Database 12c and later versions. Connections are configured through the GUI on the Configuration > Connections page. Once a connection is registered, remote tables and views are automatically discovered and appear in the catalog under the Database Tables section, where they can be browsed and queried using standard SQL with the zone.schema.table naming pattern. ## Configuration Database connections are not defined in SQL. Instead, use the Configuration > Connections page in the DeltaForge GUI to create a new Oracle connection. Provide the host, port, service name (or SID), credentials, and any schema settings. After the connection is saved and tested, the connector introspects the target schema and populates the catalog with the available tables. Once registered, remote Oracle tables can be queried directly: ```sql SELECT * FROM my_zone.hr.employees WHERE department_id = 50; ``` ## Authentication Authentication is performed using Oracle native password authentication over TCP. The connector builds a connect descriptor from the host, port, and database values. When use_sid is false (the default), the database value is used as the SERVICE_NAME in the TNS connect string. When use_sid is true, it is used as the SID. Service name connections are recommended for Oracle RAC and pluggable database (PDB) environments. Passwords are stored in the secure credential vault and never persisted in plaintext. ## Key Options The connector supports two data-access modes: - **Table mode**: Set the table option to read from a specific table within the configured schema. The connector generates a SELECT * and can push WHERE predicates and column projections down to the source, reducing data transfer over the network. - **Query mode**: Set the query option to execute an arbitrary SQL statement on the source server. This enables pre-aggregated extracts, joins across multiple schemas, and Oracle-specific features such as analytical functions. The query is sent to the source as-is. Only one mode may be active at a time. - **use_sid**: Set to true to connect using a SID instead of the default service name mode. Required for older Oracle instances that do not expose a service name through the listener. - **schema**: Overrides the default schema (owner) for unqualified table references. Defaults to the login username when omitted. - **max_connections**: Connection pool size. Connections are validated with a lightweight ping before use and automatically re-established on transient failures. - **connect_timeout_secs**: Maximum wait time for establishing a new connection.