Procedure Commands

Name

Name of the command, as it appears in the graphical interface.

Log Counter

Shows which counter (Insert, Update, Delete or Errors) will record the number of rows processed by this command.

Log level

Level of importance of the command, for consulting the execution log according to this level.

Ignore Errors

Shows that the procedure is not interrupted in case of an invalid return code. If this box is checked, the procedure command will go into "warning" instead of "error", and the procedure will not be stopped.

Command

The command launched on the data server. Two similar tabs (Command Source and Command Destination) appear in the case of a multi-connection procedure.

Technology

Technology on which the command will be executed.

Note: To use Oracle Data Integrator Tools (commands) in KM procedure commands or procedures commands, you must set the technology to Sunopsis API.
To use OS commands or to execute external programs, you must set the technology to Operating System.

Transaction Isolation

The transaction isolation level for Select orders. The isolation levels shown are those of the SQL ISO. They are not supported by all data servers.

The levels of isolation are:

• Default: The transaction keeps the connection's isolation level.

• Read Uncommitted: The transaction can read data not committed by another transaction.

• Read Commited: The transaction can only read data committed by other transactions (in general, this is the default mode of many data servers).

• Repeatable Read: The transaction is certain to read the same information if it executes the same SQL query several times, even if the rows have been modified and committed by another transaction in the meantime.

• Serializable: The transaction is certain to read the same information if it executes the same SQL query several times, even if the rows have been modified, deleted or created and committed by another transaction in the meantime.

Context

Execution context of the query. If "Execution context" is left, the command will be executed in the execution context chosen on launching or on the step.

Schema

Logical schema for execution. This logical schema, linked to the context, allows the physical execution schema to be defined.

Transaction

You can execute commands on several concurrent transactions (numbered from 0 to 9) or work off-transaction by choosing the option "Autocommit". The latter may be more efficient.

Commit

If your command is being executed in a transaction (numbered 0 to 9), you can decide to continue or to commit the current transaction according to the following modes:

• No Commit: The transaction is not committed. In this case, it can be committed in a later command. If a session ends normally, all transactions are committed by default.

• Commit: The transaction is committed.

• Commit 1000 rows: Oracle Data Integrator commits every 1000 records processed. This choice is only possible on a loading procedure command, that is, one containing a source command returning a result set and a destination command that carries out Inserts.

Command

The text of the command expressed in a native language or in a standard language (such as SQL, PL/SQL, Transact-SQL, shell, etc). You can use the expression editor, accessible through the button to the right of the text.

Warning: If the command seems to be made of random characters, then the procedure is encrypted. For more details about encryption and decryption, please read Encrypt a KM or a Procedure. Contact also the procedure's provider.

Always execute

The procedure command is executed regardless of the options values.

Options

This chart shows all options. The checkbox preceding each option shows that the procedure command is executed if the (checkbox-type) option has the value "yes".