Oracle's Direct Path interface is a way for data warehouses and data marts to perform incremental loads of detail data. The Oracle Direct Path 10g, 11g, 12c, 19c, and 21c connectors enable the integration platform to write to Oracle tables.

Oracle 11g and 12c connectors support Oracle wallet to manage public key security credentials on Oracle clients. If you have configured the Oracle client to use Oracle wallet, then you can provide only the Database Alias name and connect to the source or target within a map (User Name and Password is not required.) For information about Oracle wallet and how to create it in the client, see Using Oracle Wallet Manager section in the Oracle Database Advanced Security Administrator's Guide available at the following location:

You must have the Oracle 10g, 11g, 12c, 19c, and 21c standard 64-bit client installed on your system and you must have access to Oracle. If Oracle is installed on your local PC, the drive and directory path of your Oracle application must be included in your path. The path statement is automatically modified when your Oracle client software is installed. The Oracle Database Manager must be running.

You can connect to Oracle interfaces in the following ways:

The Oracle Direct Path connector accesses Oracle 10g, 11g, 12c, 19c, and 21c databases. The advantage of Oracle Direct Path API is that it is faster than the conventional ways of loading data into an Oracle database. Oracle's SQL loader utility uses the same API included in Oracle. Most of the Direct Path API speed comes from circumventing work done with conventional methods. Four instances make inserts into an Oracle table slow:

This connector sets field width in bytes. What actually varies is the number of characters that fit into a given field. For example, if a field width is 10 bytes and the encoding is Shift-JIS, the field can hold a minimum of 5 characters and a maximum of 10. This means that if you try to write 8 Japanese characters, data is truncated (the Kanji characters all take 2 bytes).

Mass load improves performance. This connector is faster than the standard Oracle connector, however, it works best in mass load. This means that data is committed at the end of the transformations and not for Append mode. Use Replace mode for the fastest run times; if you want to use Append, use one of the other Oracle connectors instead. See Oracle 10g, 11g, 12c, 19c, and 21c.

Restrictions on Using Direct Path Loads. In addition to the general load conditions described in Oracle’s documentation, the following conditions must be satisfied to use the direct path load method:

The following features are not available with Direct Path load:

Unicode Support for Oracle 10g, 11g, 12c, 19c, and 21c - These connectors include Unicode support for wide characters. To enable double-byte support, change the Regional and Language Options on your system to a double-byte language, such as Japanese.

Connector parts are the fields you configure to connect with a data source or target. The fields that are available depend on the connector you select. This is a target only connector. For a list of all parts for target connectors, see Specifying Target Connector, Parts, and Properties.

You can specify the following target properties:

This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. The following code pages are available:

These data types are available in Oracle Direct Path:

The following external data types are valid for scalar columns in a direct path load operation:

The following external object data types are supported:

The following table types are supported: