Manage job execution

Semarchy xDM allows you to monitor the activity of jobs running in the queue and troubleshoot errors.

Open a queue execution console

The execution console provides the details of the activity of a given queue. This information is useful to monitor the activity of jobs running in the queue, and to troubleshoot errors.

The content of the execution console is not persisted. Executions prior to opening the console are not displayed in this console. Besides, if the console is closed, its content is lost.

To open the execution console:

  1. In the Management view, expand the Job Executions node and double-click the Execution Engine node. The execution engine editor appears.

  2. Select the queue, right-click and select Open Execution Console.
    The Console view for this queue opens. Note that it is possible to open multiple execution consoles to monitor the activity of multiple queues.

In the Console view toolbar you have access to the following operations:

  • The delete Close Console button closes the current console. The consoles for the other queues remain open.

  • The purgelog Clear Console button clears the content of the current console.

  • The console Display Selected Log button allows you to select one of the execution consoles currently open.

Suspend a running job

To restart a suspended job in a queue:

  1. In the Management view, expand the Job Executions node and double-click the Execution Engine node. The execution engine editor appears.

  2. Select the queue that contains one Running Job.

  3. Right-click and then select Suspend Job.
    The job is suspending and the queue switches to the SUSPENDED status.

Suspending the job is an operation that should be performed with care, as respecting the sequence of the submitted job have strong impact on the consistency of the data in the hub.

Restart a job

To restart a suspended job in a queue:

  1. In the Management view, expand the Job Executions node and double-click the Execution Engine node. The execution engine editor appears. The suspended queue appears in red.

  2. Select the suspended queue.

  3. Right-click and then select Restart Job.
    The job restarts from the failed step. If the execution console for this queue is open, the details of the execution are shown in the Console.

Cancel a job

To cancel a suspended job in a queue:

  1. In the Management view, expand the Job Executions node and double-click the Execution Engine node. The execution engine editor appears. The suspended queue appears in red.

  2. Select the suspended queue.

  3. Right-click and then select Cancel Job.
    The job is canceled, the queue become READY and starts processing queued jobs.
    In the job logs, this job appears in Error status.

Canceling a job may leave the data in the data location in an invalid state. This operation is provided as a commodity, focusing on development and test environments. In production environments, jobs should not be canceled. If a job is suspended due to an infrastructure issue (for example, tablespace full, network failure), or if a long-running job is suspended due to suspected performance issues, the infrastructure or database state should be fixed (for example, by extending the tablespaces, restoring the network access, or recomputing the database statistics), and then the job should be restarted.

Troubleshoot job errors

When a job fails, depending on the configuration of the queue into which this job runs, it is either in a Suspended or Error status.

The status of the job defines the possible actions on this job.

  • A job in Error cannot be continued or restarted. It can be reviewed for analysis, and possible fixes will only affect subsequent jobs.

  • A Suspended job blocks the entire queue, and can be restarted after fixing the problem, or cancelled.

You have several capabilities in Semarchy xDM to help you troubleshooting issues. You can drill down in the erroneous task to identify the issue or restart the job with the Execution Console activated

To troubleshoot an error:

  1. Open the Job Logs.

  2. Double-click the log entry marked as JobLogStatus SUSPENDED Suspended or in JobLogStatus ERROR Error.

  3. Drill down into the Task Log.

  4. In the Task Log, review the Message.

  5. Click the Task Definition link to open the task definition and review the SQL Statements involved, the plugin or REST client called in this task.