Task Summary

In the

upper right corner

, the

Status

field displays the job status, which can be one of the following values:

Up and Running
. The job is running.
Running with Warning
. The job is running with a warning. This state can also occur when one or more table-specific subtasks fail but some subtasks are still running.
On Hold
. The job is in a paused state while the
Mass Ingestion Databases
(DBMI) agent is being updated.
Stopping
. The job is stopping in response to a Stop request.
Stopped
. The job was intentionally stopped.
Failed
. The job ended abnormally, the task deployment to the job failed, or one or more table-specific subtasks failed. Also, for an initial load job, the job was stopped.
Deploying
. The job is being deployed.
Deployed
. The job has been deployed.
Aborting
. The job is stopping immediately in response to an Abort request.
Aborted
. The job has been aborted.
Undeploying
. The job is being undeployed.
Undeployed
. The job has been undeployed.
Completed
. The job completed successfully.

The

diagram at the top of the page

displays the source connector type and connection name and the target connector type and connection name. It also shows the calculated data throughput, in rows per second, if the job has successfully replicated data to the target, regardless of the job's current status. If the calculated value is 0, indicating no data has flowed to the target, the throughput is not displayed.

Also, for incremental load jobs and combined initial and incremental load jobs, you can download the job execution log for the entire job run. In the

Select logs

list under the diagram, select one of the following log types:

Complete Log
. The entire log, including all types of messages. It is available for any job that ran, regardless of its state.
Error
. The error log, which includes messages only for errors that occurred. It is available for Failed jobs only. Use this log to determine the reason for the job failure, for example, the deployment failed. If the log file ends with an ellipsis (...), the log has been truncated because of its long length. In this case, download the Complete Log to see all error messages.

Then click the Download icon.

For initial load jobs, you can get the job log for a specific source object from the

Object Detail

tab.

Under

Overview

, review summary information about the job.

The circle image displays the number of subtasks on source tables by status. The color of the circle's rim corresponds to the status.

The following table describes the summary job properties and statistics:

Property	Description
Runtime Environment	The name of the runtime environment that the job uses to run.
Task Name	The name of the associated ingestion task. You can click the task-name link to view or edit task details in Mass Ingestion, if necessary. If you edit the task, you must redeploy it for the updated task definition to be used for a job.
Load Type	The type of load operation that the job performs. Options are: Initial Load . Loads a snapshot of source data read at a specific point-in-time to a target. Incremental Load . Loads incremental data changes to a target on a continuous basis, until the job is stopped or ends. Initial and Incremental Load . Performs an initial load and then automatically switches to an incremental load.
Task Type	The type of task, which is Database Ingestion Task .
Task Location	The project or project folder that contains the ingestion task definition.
Started By	The name of the user who started the job.
Records Read	The number of records that were read from the source. For a combined initial and incremental load job, the Records Read count might be greater than the total number of object-level DML change records written. This behavior occurs because the initial load or resync processing always starts after change data capture has begun. As a result, some change records are included in the Records Read count and then discarded before initial load or resync processing starts. These discarded records cause the Records Write count to be less than the Records Read count.
Records Written	The number of records that were successfully replicated to the target. The Records Written value might be different from the Records Read value if source records are discarded. For example, in a combined initial and incremental load job, change records read from the source before the initial unload phase completes are discarded because they're not yet needed.
Subtasks	The number of subtasks that the database ingestion job used to replicate data from source tables to the target. When a job runs, it uses a separate subtask to process each source table.
Capture Progress	For incremental load and combined initial and increment load jobs, the date and time in the source change stream to which capture processing has progressed, as shown in the time zone of the user profile.
Schedule	For initial load jobs, the name of the schedule that is used to run the job or "No schedule" if you run the job manually.
Duration (Lower left corner)	The amount of time, in the hh:mm:ss format, that the job ran before it ended.
Start Time (Lower left corner)	The date and time when the job was deployed.
End Time (Lower left corner)	The date and time when the job ended because it completed processing, was stopped, or failed. This field is not displayed for running jobs

Object Detail

Alerts

Any Time
for all stored alerts.
Today
for alerts issued today from midnight to 11:59 pm.
Last Week
,
Last Month
, or
Last Year
to show alerts from the beginning of last week, month, or year to present.
Custom
to specify a custom date range that consists of a beginning date and time and an ending date and time.