Reference

To use the Oracle connector successfully, you might need detailed information, such as information about data type mappings, stage properties, and supported read and write methods.

Runtime mappings between InfoSphere DataStage columns and SQL statement parameters
When the connector exchanges data with an Oracle database, the connector assumes that the data for each column conforms with the data type definition that is specified for that column on the link.
Data type mapping and Oracle data types
When the Oracle connector imports a table definition, the connector converts Oracle data types to IBM® InfoSphere® DataStage® data types. When the Oracle connector creates a table by issuing an SQL statement that is specified in the Create table statement property, the connector converts InfoSphere DataStage data types to Oracle data types.
Properties for the Oracle connector
Use these options to modify how the connector reads and writes data.
Runtime column propagation
Use runtime column propagation to have the connector automatically add missing columns to the link schema when the job runs.
Partitioned read methods
The Oracle connector supports these partitioned read methods: rowid range, rowid round robin, rowid hash, modulus, minimum and maximum range, and Oracle partitions.
Oracle connector partition type
For writes to a range-partitioned, list-partitioned or interval-partitioned table, the Oracle connector partition type ensures that the distribution of input records matches the organization of the partitions in the table.
Supported write methods
When you configure the Oracle connector as a target, you can use the supported write methods to write rows to an Oracle table or writable view.
Reject conditions
When you use the Oracle connector as a target in a job, you can add a reject link and send rejected records to a target stage. Reject conditions determine when a record is rejected.
White space characters, NULL values, and empty string values
When the Oracle connector reads data from a database or writes data to a database, the connector always preserves white space characters such as SPACE, TAB, CR (carriage return), and LF (line feed). In addition, the connector does not trim leading or trailing white space characters from text values unless the Preserve trailing blanks property is set to No.
Dictionary views
To complete specific tasks, the Oracle connector requires access to a set of Oracle dictionary views.
Exceptions table
If you configure the connector to enable constraints after bulk loading data, the connector stores the ROWID values for any rows that violate the constraints in an exceptions table.
Environment variables that the Oracle connector uses
In addition to the environment variables that affect how the Oracle connector operates, the Oracle connector queries and uses Oracle environment variables and environment variables for the local operating system.

Parent topic: Oracle connector