Write

None.

• When processing data, the Oracle Bulk Load Snap executes in an infinite loop when database storage reaches its full capacity.
• 1438090 Snap does not support Kerberos authentication for Oracle.

Columns in a table that do not contain actual values but are generated based on a formula are referred as virtual columns. Tables containing virtual columns cannot be bulk loaded using this Snap. The table must only contain actual values to be bulk loaded. A workaround for this issue is to use a view that specifies only the non-virtual columns and use that view for the bulk load. For more information about creating a view in the Oracle database, refer to Creating a view in Oracle database.

Does not work in Ultra Pipelines. 

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Oracle Account for information on setting up this type of account.

If the table does not exist when the Snap tries to do the load, and the Create table property is set, the table will be created with the columns and data types Required. to hold the values in the first input document. If you would like the table to be created with the same schema as a source table, you can connect the second output view of a Select Snap to the second input view of this Snap. The extra view in the Select and Bulk Load Snaps are used to pass metadata about the table, effectively allowing you to replicate a table from one database to another.
 

The table metadata document that is read in by the second input view contains a dump of the JDBC DatabaseMetaData class. The document can be manipulated to affect the CREATE TABLE statement that is generated by this Snap. For example, to rename the name column to full_name, you can use a Mapper (Data) Snap that sets the path $.columns.name.COLUMN_NAME to full_name.  The document contains the following fields:

• columns - Contains the result of the getColumns() method with each column as a separate field in the object. Changing the COLUMN_NAME value will change the name of the column in the created table. Note that if you change a column name, you do not need to change the name of the field in the row input documents. The Snap will automatically translate from the original name to the new name. For example, when changing from name to full_name, the name field in the input document will be put into the "full_name" column. You can also drop a column by setting the COLUMN_NAME value to null or the empty string.  The other fields of interest in the column definition are:

  • TYPE_NAME - The type to use for the column.  If this type is not known to the database, the DATA_TYPE field will be used as a fallback.  If you want to explicitly set a type for a column, set the DATA_TYPE field.

  • _SL_PRECISION - Contains the result of the getPrecision() method.  This field is used along with the _SL_SCALE field for setting the precision and scale of a DECIMAL or NUMERIC field.

  • _SL_SCALE - Contains the result of the getScale() method.  This field is used along with the _SL_PRECISION field for setting the precision and scale of a DECIMAL or NUMERIC field.

• primaryKeyColumns - Contains the result of the getPrimaryKeys() method with each column as a separate field in the object.

• declaration - Contains the result of the getTables() method for this table. The values in this object are just informational at the moment.  The target table name is taken from the Snap property.

• importedKeys - Contains the foreign key information from the getImportedKeys() method. The generated CREATE TABLE statement will include FOREIGN KEY constraints based on the contents of this object. Note that you will need to change the PKTABLE_NAME value if you changed the name of the referenced table when replicating it.

• indexInfo - Contains the result of the getIndexInfo() method for this table with each index as a separated field in the object.  Any UNIQUE indexes in here will be included in the CREATE TABLE statement generated by this Snap.

Available insert modes when loading data into table.

• INSERT - Load rows only if the target table is empty.
• APPEND - If data already exists in the table, the new rows are appended to the table. If data does not already exist, the new rows are simply loaded.
• REPLACE - First delete all the rows in the existing table and then load rows.
• TRUNCATE - First truncate the table and then load rows.

Default Value: APPEND
See this doc for more information.

Specify the maximum number of rows which can fail before the bulk load operation is stopped.

Default Value: 50 
Example:10 (if you want the Pipeline execution to continue as far as the number of failed records are less than 10)

Select this check box to use direct path load mode of SQLLDR program. Typically, used when loading large data sets. This substantially improves the bulk load performance by reducing loading time.

Default Value: Selected 

Select this checkbox to skip virtual columns to prevent errors while loading data.

Default Value: Selected

Use this field set to define additional SQL Load parameters if any. This field set contains Param Name and Param Value fields.

Choose the parameter name for SQL. Available options are:

• BINDSIZE
• COLUMNARRAY ROWS
• DIRECT
• LOAD
• MULTITHREADING
• PARALLEL
• READSIZE
• RESUMABLE
• RESUMABLE_NAME
• RESUMABLE_TIMEOUT
• ROWS
• SILENT
• SKIP
• SKIP_INDEX
• MAINTENANCE
• SKIP_UNUSABLE_INDEXES
• STREAMSIZE

See SQL* Loader parameters for more information.

Default Value: N/A
Example: COLUMNARRAYROWS

Specify the value for the parameter selected above.

Default Value: N/A
Example: 2000

Specify or select the name of the column in the table that you want to load.

Default Value: N/A
Example: DESCRIPTION, MESSAGE_BODY

Specify a value (in bytes) for the column length.

Default Value: N/A
Example: 10