Oracle
Oracle datasources use theOracle 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 intable_options describes a table to query:
Complete example
Connection
Dataset
Authentication modes
Theauth_mode field supports Oracle authentication modes for privileged connections:
Schema-qualified tables
When theschema 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:
MARKET_DATA.DAILY_TRADES rather than relying on the user’s default schema.
Microsecond timestamp precision
OracleTIMESTAMP(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 theSEC_CASE_SENSITIVE_LOGON parameter).
Table not found (ORA-00942)
Check that the user hasSELECT 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:Slow queries
- Increase
batch_sizefor large result sets (up to100000). - 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 thanDATE(which only supports second precision).

