|Type of Support:||Read & Write; In-Database|
|Validated On:||12c, 12.01.00.01|
|Connection Type:||ODBC, OLEDB, and OCI (32- and 64-bit)|
|Driver Details:||The OCI driver can be downloaded from Oracle Instant Client.
Bulk write support is available with 64-bit connections for standard and in-database workflows.
In-Database processing requires 64-bit database drivers.
Alteryx tools used to connect
- Input Data Tool and Output Data Tool (for standard workflow processing)
- Connect In-DB Tool and Data Stream In Tool (for In-Database workflow processing).
Connecting to Oracle
Version 10.02.00.01 64-bit OLEDB provider had issues with FIXED DECIMAL. Alteryx recommends using the 11g or newer driver.
- Oracle Connection uses the Oracle Call Interface (OCI) library to connect to the Oracle database. This library is part of the Client software installed with the database.
Oracle OLEDB is not supported in the In-Database tools. Use ODBC or OCI.
Alteryx supports multi-line, multiple SQL statements for Oracle Stored Procedures. The Alteryx engine is not used when executing a stored procedure. This execution happens entirely on the database server.
To access stored procedures for your connection:
- Drag the Input, Output, or Run Command tool onto the Alteryx Designer canvas.
- Select the Connect a File or Database menu, and then select the Oracle database connection.
- In the Input Data Configuration window, select Pre SQL Statement or Post SQL Statement. You can enter one or more statements in the SQL Editor tab, or you can select from a list of Stored Procedures.
In the Configure Pre SQL Statements or Configure Post SQL Statements window and Stored Procedures tab, view the Parameter, Datatype, and then enter the Value for each stored procedure parameter for OCl, ODBC, and OLEDB connection. Select the desired Stored Procedure and click OK.
- Selecting a stored procedure will overwrite what is in the field. Stored procedures cannot be accessed for an Oracle connection from the Table or Query file format options menu.
- Only stored procedures with IN parameters will be listed.
- Oracle data types may differ in how they map to Alteryx, depending on whether the connection is OLI, ODBC, or OLEDB.
- String parameters must have single quotes around the entered value.
- The SQL syntax for calling the stored procedure in Oracle should be in the format of CALL "sproc_name" (optional parameter1, optional parameter2, ...).
- When used in an Input, the Value must represent a value within the database.
- You can select whether you want the SQL Editor or Stored Procedures tab to open by default. The default tab is Stored Procedures if there is not text in the SQL Editor tab.
Unsupported Data Types
The following data types are unsupported and cannot be entered into the Stored Procedures Parameter value field:
- Binary types: RAW, LONG RAW, and BLOB
If your stored procedure contains an unsupported data type, then:
- Designer sets the data type to unsupported.
- The value column in the data grid will become read-only and the OK button will be disabled, indicating that the stored procedure cannot be run.
Maximum Columns In Table: 1000
Maximum Column Name Length: 30 characters
Maximum Row Size: 4GB ( does not include LOB size )
Variable length strings may return NULL instead of Empty.
All versions - INT64 is transported as a Fixed Numeric; SQL_C_BIGINT is not supported.
10.02.00.01 64 bit - issues with FIXED DECIMAL
Int64 is transported as a Double.
Bool is transported as a String(1)
DateTime is transported as a String(19)
- A single workflow with ODBC connections cannot contain either OleDB or OCI connections using the same driver.
If you are connecting to an Oracle database that contains Unicode® encoded data, select Force SQL WChar Support in the Input Data Tool Configuration window. Character columns are then treated as SQL_WCHAR, SQL_WVARCHAR, or SQL_WLONGVARCHAR.