Current Run Tab
1.
The Current Run
tab displays a list of queued, running, and failed current ETL processes in the
top window.
2.
This list includes
comprehensive information about each process.
3.
Once an ETL process completes, it is
accessible from the Run History tab.
The execution plan whose runtime
instance is this record. This field is read only.
The status of the run. The possible
values are the following.
Value
|
Description
|
Queued
|
Tasks for which the Depends On
tasks are not yet completed. Displayed in yellow in the Current Run list.
|
Runnable
|
Tasks for which the Depends On
tasks have completed and are ready to be run but are waiting for an
Informatica slot to be available.
|
Running
|
Tasks for which the Depends On
tasks have been completed, have gotten an Informatica slot, and are being
executed. Displayed in blue.
|
Paused
|
Task group members that are
waiting for the other tasks in the group to be executed.
|
Failed
|
Tasks that were executed but
encountered a problem. Displayed in red.
|
Stopped
|
Tasks for which one or more
Depends On tasks have failed.
|
Completed
|
All tasks have completed without
errors. Displayed in green.
|
Start time of the ETL process.
Reflects the start time of every ETL attempt. For example, if the ETL fails and
is run again, it gets a new start timestamp. The history of attempted runs is
maintained in the audit trail for the run. This field is read only.
End time of the ETL process.
Reflects the end time of every ETL attempt. For example, if the ETL fails and
is run again, it gets a new start timestamp. The history of attempted runs is
maintained in the audit trail for the run. This field is read only.
A calculated field that shows the
difference between start and end time stamps.
Displays messages generated during
run time. You can add notes to this field for Completed runs.
ID for the process. This value is an
integer that is incremented by 1 for every run. This value is stored as
ETL_PROC_WID in all the data warehouse tables. This field is read-only.
The total number of tasks for this
run. This field is read only.
The sum total of tasks that have
failed and that have stopped. This field is read only.
The number of tasks whose status is
Completed. This field is read only.
The number of tasks whose
prerequisite tasks have not completed, and the number of tasks whose
prerequisite tasks are completed and are waiting for resources. This field is
read only.
The name of the scheduled ETL
process.
The Audit Trail (RO) subtab is a
read-only tab that provides the history of the selected run.
The date the selected run was last
updated.
Start time of the selected run.
End time of the selected run.
The difference between the start
timestamp and the end timestamp of the selected run.
Status of the selected run.
The Summary (RO) subtab provides a
summary (based on dynamic SQL) of the selected ETL run.
The task phase of the selected ETL
run.
Start time of the selected phase of
the run.
End time of the selected phase of
the run.
The difference between the start
timestamp and the end timestamp of the selected phase of the run.
The Run Type Summary (RO) subtab is
a read-only tab that indicates the number of task details by the execution
type.
The Tasks subtab displays runtime
instances of the tasks. As the execution proceeds, the tasks are executed based
on the dependency rules and some prioritization.
As tasks complete, the tasks that
depend on the completed tasks are notified and once their dependencies are
completed, they become eligible to run. If a task fails, the administrator can
address the failure and then requeue the task or mark it as completed. The DAC
server polls for any changes in the failed task's detail status. If a failed
task detail is queued, the task itself gets back into the ready-to-run queue
and all its dependent tasks get into the queued status.
The rules of the prioritization are
as follows:
- Tasks with no dependencies are executed first.
- If a task has failed and has been requeued, it gets the maximum priority.
- Tasks with greater phase priorities are executed next. When several tasks of the same phase are eligible to run, the tasks with greater task priorities are executed next. The prioritization is also based on the number of dependent tasks, the number of source tables, and the average time taken by a task.
The Task Details subtab opens in
Query mode. It enables you to query for tasks associated with the selected ETL
run in order to view execution details.
No comments:
Post a Comment