5.2.26. Oracle OCI Connector

<< Click to Display Table of Contents >>

Navigation:  5. Detailed description of the Actions > 5.2. Input Actions >

5.2.26. Oracle OCI Connector

Icon: clip0459


Function: OracleOCI


Property window:



Short description:


Extract data from Oracle.


Long Description:


This action runs some SQL command to extract data from Oracle (i.e. it also runs any free-text SQL command inside Oracle).




There are, basically, two reasons why you might be interested in using this Oracle OCI Action rather than the standard ReadODBC action (from the sections 5.1.6, and 5.2.2) to extract data from Oracle:
1. If you want a better control on the connection “timeouts”: For very large extractions (i.e. an extraction of several TB), you’ll quickly notice that the ReadODBC action generates a large quantity of “timeout” errors. In opposition, the Oracle OCI Action is a lot more stable and reliable. This action actually uses the same exact same libraires (i.e. the OCI libraries) that are also used inside the “SQLPlus” tool to connect to Oracle (this tool is recognized to be the most stable and most efficient way to interact with Oracle).
2. The easiest way to connect Anatella to Oracle under Linux (inside Wine) is through this Oracle OCI Action (i.e. the setup of the ODBC connection for Oracle inside Wine is *much*        more difficult)

You can use the “>” character at the start of the SQL field (parameter P4) to create dynamically the SQL command to execute (using Javascript and some Global Parameters). You’ll find more details on “Graph Global Parameters” in the section 5.1.5.

Before using this action, you first need to download the additional Oracle OCI components (it’s a 196MB download): i.e. Click the blue URL (parameter P5) to automatically download and install the Oracle OCI components.

The parameter P1 (named "Connection String") can be a reference to the file "TNSNAMES.ORA", or it can be directly the contents of the file "TNSNAMES.ORA". For example, a "Connection String" such as this one is perfectly valid:




The parameter P6 represents the number of rows that are extracted "in one block" out of the database. A higher value is better because it extracts larger "blocks of rows" and thus minimizes round trips of network data transfers (and thus the extraction runs faster). Do not put a value too high neither, otherwise the Oracle drivers may crash (and it also consumes a little more RAM).