4.62 ALL_SCHEDULER_RUNNING_CHAINS
ALL_SCHEDULER_RUNNING_CHAINS
displays information about the chain steps of the running chains accessible to the current user (that is, those chains that the user has ALTER
privileges for). In the case of nested chains, this view also enables you to traverse the hierarchy of the chain with a SQL statement that contains a CONNECT BY
clause linking up the JOB_SUBNAME
and STEP_JOB_SUBNAME
columns.
Related Views
-
DBA_SCHEDULER_RUNNING_CHAINS
displays information about the chain steps of all running chains in the database. -
USER_SCHEDULER_RUNNING_CHAINS
displays information about the chain steps of the running chains owned by the current user. This view does not display theOWNER
column.
Column | Datatype | NULL | Description |
---|---|---|---|
|
|
|
Owner of the job which is running the chain |
|
|
|
Name of the job which is running the chain |
|
|
|
Subname of the job which is running the chain (for a nested chain), else NULL |
|
|
|
Owner of the chain being run |
|
|
|
Name of the chain being run |
|
|
|
Name of the step of the running chain |
|
|
|
State of the running chain step:
|
|
|
|
Error code with which the step completed (if it has completed) |
|
|
|
Indicates whether the running chain step has completed ( |
|
|
|
Date when the running chain step started (if it has started) |
|
|
|
Date when the running chain step stopped (if it has stopped) |
|
|
|
Amount of time it took the chain step to complete (if it has completed) |
|
|
|
Indicates whether the chain step should be skipped ( |
|
|
|
Indicates whether the chain step should be paused after running ( |
|
|
|
Indicates whether the chain step should be paused before running ( |
|
|
|
Indicates whether the chain step will be restarted on database recovery ( |
|
|
|
Indicates whether the chain step will be restarted on application failure ( |
|
|
|
Subname of the job running the step |
|
|
|
Log ID of the job running the step |
See Also: