You can create connections to one or more Oracle Database from Trifacta® Self-Managed Enterprise Edition.
Tip: You can create connections to databases of this type that are managed by your enterprise or are hosted in cloud infrastructure. The required configuration is the same. The cloud-based version is labeled on Amazon RDS . In the Create Connection dialog, you can search for that term.
NOTE: You cannot disable type inference for Oracle sources. This is a known issue.
Supported Versions: 18.104.22.168
Trifacta Self-Managed Enterprise Edition
NOTE: Dots (.) in the names of Oracle tables or table columns are not supported.
- If you haven't done so already, you must create and deploy an encryption key file for the Trifacta node to be shared by all relational connections. For more information, see Create Encryption Key File.
If you are connecting to the Oracle Database using SSL, additional configuration is required in Oracle Database .
Trifacta Self-Managed Enterprise Edition supports the use of the following SSL ciphers to communicate with Oracle Database :
For more information, please see the documentation that is provided with your Oracle distribution.
To create this connection:
- In the Import Data page, click the Plus sign. Then, select the Relational tab. Click the Oracle Database card.
- You can also create connections through the Connections page. See Connections Page.
For additional details on creating an Oracle Database connection, see Relational Access.
Modify the following properties as needed:
Enter your hostname. Example:
|Port||Set this value to |
|Connect String options|
Please insert any connection options as a string here. See below.
Select the option if the connection should use SSL.
NOTE: Additional configuration may be required in the database server. For more information, please consult the documentation that was provided with the distribution.
NOTE: Additional configuration is required. See Configure Data Service.
|Service Name||Enter the name of the Oracle service.|
|User Name||(basic credential type only) Username to use to connect to the database.|
|Password||(basic credential type only) Password associated with the above username.|
|Test Connection||After you have defined the connection credentials type, credentials, and connection string, you can validate those credentials.|
|Connection Name||Display name of the connection|
|Connection Description||Description of the connection, which appears in the application.|
The properties that you provide are inserted into the following URL, which connects Trifacta Self-Managed Enterprise Edition to the connection:
Connect string options
The connect string options are optional. If non-standard connections are required, Oracle Database supports using tsnames format.
When the connect string options field is used:
- The connect string options parameters are prepended with
- The following fields are ignored from the form. These values must be specified as part of the tsnames :
After you specify the connect string options, the generated connection URL is automatically prepended with the following protocol information. Do not add this to the connection URL or connect string options:
Examples are below.
If you are using a service identifier, instead of a service name, please specify your connection string options as follows:
If TCPS protocol is required, you can specify your connection string options as follows:
For more information, please see the documentation for the Oracle Database driver.
This connection uses the following driver:
- Driver version:
- Driver documentation: https://docs.oracle.com/en/database/oracle/oracle-database/19/index.html
Create via API
This connection can also be created using the API.
For more information, see https://api.trifacta.com/ee/9.2/index.html#operation/createConnection
For more information on common error messages, see https://docs.oracle.com/cd/E11882_01/java.112/e16548/apxermsg.htm#JJDBC28962.
"Could not create dataset - Lexical error"
When you attempt to create a dataset with SQL from an Oracle database, you may receive an ORA error similar to the above. These queries may work in other database tools.
The solution is to apply aliasing impacted columns in your SQL query. For more information, see Supported SQL Syntax.
The following syntax requirements apply to this connection.
Object delimiter: double-quote
Double quotes required around database and table names and not required around column names.
For more information on SQL in general, see Supported SQL Syntax.
For more information on how values are converted during input and output with this database, see Oracle Data Type Conversions.
This page has no comments.