Use to view the session step details.
A session step is the unit of execution found between a task and a session. It corresponds to a step in a package or in a scenario. When executing a mapping or a single variable, for example, a session has only one session step.
The Session Step Editor has the following tabs:
| Properties | Description |
|---|---|
| Step Name | Name of the step executed. |
| Status | Status when the Session Step Editor was opened. The possible states are Done, Error, Running, Waiting, and Warning. |
| Step Type | Type of step executed. More |
| Context | Context in which the step was executed. |
| Order Number | Order number linked to the step for this session. |
| Number of Executions | Execution number, in the event of successive executions of the step (loops). |
| URL | An optional URL link that enables you to view details such as execution structure, metrics, error messages, and logs using a UI specific to the execution. For example, Oozie Web Console or MapReduce JobTracker. |
| Properties | Description |
|---|---|
| No. of Inserts | Number of rows inserted during the step. |
| No. of Updates | Number of rows updated during the step. |
| No. of Deletes | Number of rows deleted during the step. |
| No. of Errors | Number of rows in error in the step. |
| No. of Rows | Total number of rows handled during this step. |
| Maximum number of errors allowed |
When this field is left empty, then an infinite number of errors is allowed. When this number or percentage of errors is exceeded, the step goes into error status. |
| Properties | Description |
|---|---|
| Start | Start date and time of execution of the step. |
| End | End date and time of execution of the step. |
| Duration (seconds) | Time taken for execution of the step. |
| Return code | Return code for the step. |
Note: The target table details are only provided for session steps in which a mapping has been executed or a datastore check has been performed.
| Properties | Description |
|---|---|
| Table Name | Name of the target datastore. |
| Model Code | Code of the model in which the target datastore is stored. |
| Resource Name | Resource name of the target datastore. |
| Logical Schema | Logical schema of this datastore. |
| Forced Context Code | Context of the target datastore. |
Note: If tracking was not enabled for this session, this section will be empty.
| Properties | Description |
|---|---|
| Name | Full name of the variable or sequence. |
| Type | Indicates whether this is a variable or a sequence. |
| Value | Value associated with the variable or sequence at the end of the session step. For sequences, the value shows the start and end value of the sequence used in this step. |
| Properties | Description |
|---|---|
| Filter By | Filters Knowledge Modules by LKM, IKM and CKM, which are used in Session Step. |
| Knowledge Module | Displays all Knowledge Modules used in Session Step depending on the selection in the Filter By field. |
| Options | Displays all options available for the selected Knowledge Module. |
| Name | Name of the option. |
| Value | Value of the option. |
| Use Default | Indicates whether the content in the Value field is default value or not. |
Step execution error message, if any.
Use to view a summary of the Oozie or MapReduce job details when a session step is executed within a Hadoop cluster.
| Properties | Description |
|---|---|
| External ID | ID representing the execution in the external system, for example, an Oozie Job ID when the execution is in Oozie. |
| Last Refresh | Last time the execution log details were refreshed. |
| Properties | Description |
|---|---|
| Execution Details | Displays optional text summarizing the execution with details from the external system. It might also contain embedded links to native UIs for the external system, such as the Oozie Web Console and MapReduce JobTracker. |
"Monitoring Integration Processes" in Oracle Fusion Middleware Administering Oracle Data Integrator
Oracle Fusion Middleware Integrating Big Data with Oracle Data Integrator