Connecting to Oracle

This section contains details for Oracle connections.

General information

Field Description
Data source Oracle
Supported versions

Connection string jdbc:oracle:thin




Supported features
Estimate job


Analyze data




Processing capabilities


Spark agent


Yarn agent


Parallel JDBC


Java Platform version compatibility


JDK 11


Minimum user permissions

In order to bring your Oracle data into Collibra Data Quality & Observability, you need the following permissions.

  • Read access on Oracle database tables.
  • The Kerberos user has read permissions on Oracle tables (if using Kerberos authentication)
  • ROLE_ADMIN assigned to your user in Collibra DQ.

Recommended and required connection properties

Required Connection Property Type Value


Name Text The unique name of your connection. Ensure that there are no spaces in your connection name.


Connection URL String

The connection string path of your Oracle connection.

When referring to the example below, replace the ${value} sections of the connection URL with your actual value.

Example Using SID


Example Using database service name



Driver Name String

The driver class name of your connection.



Port Integer

The port number to establish a connection to the datasource.

The default port is 1521


Source Name String N/A


Target Agent Option The Agent that submits your Spark job for processing.


Auth Type Option

The method to authenticate your connection.

Note The configuration requirements are different depending on the Auth Type you select. See Authentication for more details on available authentication types.


Driver Properties String

The configurable driver properties for your connection. Multiple properties must be comma delimited. For example, abc=123,test=true

Connection properties recognized by Oracle JDBC drivers

Name Short Name Type Description
user n/a String The user name for logging into the database
password n/a String The password for logging into the database
database server String The connect string for the database
internal_logon n/a String A role, such as sysdba or sysoper, that allows you to log on as sys
defaultRowPrefetch prefetch String (containing integer value) The default number of rows to prefetch from the server (default value is "10")
remarksReporting remarks String (containing boolean value) "true" if getTables() and getColumns() should report TABLE_REMARKS; equivalent to using setRemarksReporting() (default value is "false")
defaultBatchValue batchvalue String (containing integer value) The default batch value that triggers an execution request (default value is "10")
includeSynonyms synonyms String (containing boolean value) "true" to include column information from predefined "synonym" SQL entities when you execute a DataBaseMetaData getColumns() call; equivalent to connection setIncludeSynonyms() call (default value is "false")
processEscapes n/a String (containing boolean value) "false" to disable escape processing for statements (Statement or PreparedStatement) created from this connection. Set this to "false" if you want to avoid many calls to Statement.setEscapeProcessing(false);. This is espcially usefull for PreparedStatement where a call to setEscapeProcessing(false) would have no effect. The default is "true".
defaultNChar n/a String (containing boolean value)

"false" is the default. If set to "true", the default behavior for handling character datatypes is changed so that NCHAR/NVARCHAR2 become the default. This means that setFormOfUse() won't be needed anymore when using NCHAR/NVARCHAR2. This can also be set as a java property :java -Doracle.jdbc.defaultNChar=true myApplication

useFetchSizeWithLongColumn n/a String (containing boolean value)

"false" is the default.

Important  This is a thin-only property and should not be used with any other drivers.

If set to "true", the performance when retrieving data in a 'SELECT' will be improved but the default behavior for handling LONG columns will be changed to fetch multiple rows (prefetch size). It means that enough memory will be allocated to read this data. So if you want to use this property, make sure that the LONG columns you are retrieving are not too big or you may run out of memory. This property can also be set as a java property : java -Doracle.jdbc.useFetchSizeWithLongColumn=true myApplication

SetFloatAndDoubleUseBinary n/a String (containing boolean value)

"false" is the default. If set to "true", causes the java.sql.PreparedStatment setFloat and setDouble API's to use internal binary format as for BINARY_FLOAT and BINARY_DOUBLE parameters. See oracle.jdbc.OraclePreparedStatement setBinaryFloat and setBinaryDouble


Select an authentication type from the dropdown menu. The options available in the dropdown menu are the currently supported authentication types for this data source.

Required Field Description



The username of your Oracle account.



The password of your Oracle account.



The Kerberos entity to authenticate and grant access to your connection.

Example [email protected]



The file path of the keytab file that contains the encrypted key for a Kerberos principal.

Example /tmp/keytab/oracle_user.keytab

Important You must update your keytab secrets file with the following values.

Key: cdq_user.keytab

Label: base64 encoded string


Password The secret credential associated with your Kerberos principal.



The file path that contains the script file used to interact with and authenticate a Kerberos user.

Example /tmp/keytab/


Param $1 Optional. Additional Kerberos parameter.


Param $2 Optional. Additional Kerberos parameter.


Param $3 Optional. Additional Kerberos parameter.


TGT Cache The ticket-granting ticket cache that stores the TGT to authenticate your connection.


  • There is an Apache Spark limitation where Pullup jobs on Oracle datasets that use Timestamp with Time Zone column types fail in the LOAD activity. For more information about the limitation and a workaround, see the support article.
  • Because Oracle normally converts all characters in table and schema names to uppercase, Oracle also treats lower case characters as special characters. A possible workaround is to do the following:
    1. Go to Explorer and click Create DQ Job on an Oracle table.
    2. In the Query box, wrap the schema and table name with double quotes ". For example, select * from "schema"."tablename".
    3. Go to the Run page and click the Run CMD tab.
    4. Click the lock icon to unlock the command line.
    5. Wrap backslashes \ around the double quoted schema and table names, and add a whitespace before the ending double quote of the -q section. For example, -q "select * from \"schema\".\"table\" "
  • The SDO_GEOMETRY column data type is not supported on Oracle connections.