Skip to main content

Oracle

Oracle datasources use the Oracle database driver in thin mode. No Oracle Instant Client installation is required.
See Supported Data Formats for database source categories and schema column types supported on Oracle connections.

Connection configuration

URI format

Required fields

Optional fields

Environment variables

Example connection

Dataset configuration (data_args)

Required fields

Optional fields

table_options entry

Each entry in table_options describes a table to query:

Complete example

Connection

Dataset

Oracle column names are uppercase by default. Use uppercase names in your schema definition and data_args fields to match Oracle’s metadata.

Authentication modes

The auth_mode field supports Oracle authentication modes for privileged connections:
Using SYSDBA authentication in production datasource connections is not recommended. Create a dedicated read-only user with SELECT privileges on the required tables.

Schema-qualified tables

When the schema field is set on the connection, CloudQuant Data Liberator queries tables within that schema. This is useful when the database user’s default schema differs from where the data resides:
This queries MARKET_DATA.DAILY_TRADES rather than relying on the user’s default schema.

Microsecond timestamp precision

Oracle TIMESTAMP(6) columns support microsecond precision. A custom-patched oracledb 3.4.0 is available for CloudQuant Data Liberator that preserves full microsecond precision during data extraction.
The standard Oracle database driver 3.3+ driver supports microsecond timestamps. The custom-patched 3.4.0 build provides additional optimizations for high-frequency timestamp extraction. Contact your CloudQuant Data Liberator administrator for the patched driver.

Driver and dependencies

Thin mode connects directly to Oracle without requiring Oracle Instant Client. This simplifies deployment and eliminates native library dependencies.

Troubleshooting

Connection refused

Verify the Oracle listener is running and accepting connections on the specified host and port:

ORA-12514: TNS listener does not currently know of service

The service name in the URI does not match any registered service on the Oracle listener. Verify the service name:

ORA-01017: invalid username/password

Ensure the username and password are correct. Oracle passwords are case-sensitive (depending on the SEC_CASE_SENSITIVE_LOGON parameter).

Table not found (ORA-00942)

Check that the user has SELECT privileges on the target table and that the schema is correctly specified:

Debug timing

To enable debug timing for Oracle query boundaries, set the environment variable:
This logs timing information for each query phase, useful for diagnosing performance bottlenecks.

Slow queries

  • Increase batch_size for large result sets (up to 100000).
  • Ensure the datetime and key columns are indexed in Oracle.
  • For partitioned tables, verify that Oracle partition pruning is being used by checking the execution plan.
  • Use TIMESTAMP(6) columns for microsecond precision rather than DATE (which only supports second precision).