7/27/2019 FSS BW Operations - Mannually Killing a Job

1/8

Manually Killing a job

Document Version / Dtails : Ver 1.0 / 15-Feb-2011

Record Of Release

VersionNo.

Created /Modified By

Reviewed By Release Date Modifications Done

1.0 Saurabh/Sanjay

Kush Kashyap 15/02/2011 Modified Step 10.

Project ID: E6806 Project Name: FSS BW Operation

7/27/2019 FSS BW Operations - Mannually Killing a Job

2/8

Manually Killing a job

PM-03-04

Ver 1.0/14-Aug-08

Page 2 of 8

Scope of Document: This document helps us to understand the steps to be followed in case we encounterany type of delay in execution of any process chain step. Sometime due to system performance issue any

process chain step may hang for a long time. In that case we need to kill that job and restart it. But thisoption should be used only when then there no other option is left and should be done carefully.

In this case we have taken the example of Delete Index Process chain step of process chainGBS_EDW_TO_ADM_DAILY. Normally Delete Index process step takes 30-45 minutes to execute but in thiscase it has taken more than 2 hours. So here we will kill the job and restart it again.

Step1: Identify the process chain step getting delayedIn this case we found that the Delete Index process chain step has taken more than 2.5 hrs and is still notcompleted. So we will kill this job and restart it again.

7/27/2019 FSS BW Operations - Mannually Killing a Job

3/8

Manually Killing a job

PM-03-04

Ver 1.0/14-Aug-08

Page 3 of 8

Step2: Right click on the process chain step and click on Displaying Messages. Below screen will appear.

Now go to Backg tab. On Backg tab, click on Batch Monitor.

Step3: After clicking on Batch Monitor, Job Overview screen will appear. Onjob Overview screen click onjob name.

7/27/2019 FSS BW Operations - Mannually Killing a Job

4/8

Manually Killing a job

PM-03-04

Ver 1.0/14-Aug-08

Page 4 of 8

Step4: After clicking on Job name, the job coressponding to the Drop Indexes process step

(BI_PROCESS_DROPINDEX in this case) will be displayed as below. Click on Job Details tab.

Step5: After clicking on Job Detail tab, Detailed Information window for the related job will open. It willbe having the Executing Server name and WP number/PID details. Note down these details.

7/27/2019 FSS BW Operations - Mannually Killing a Job

5/8

Manually Killing a job

PM-03-04

Ver 1.0/14-Aug-08

Page 5 of 8

Step6: Open new session and Go to Transaction SM51.

Step7: After running the transaction SM51, Sap Servers screen will appear. It will show the list of all theactive SAP application servers.

Step8: Find out the server name from SAP servers list which you noted down from job detail screen.

7/27/2019 FSS BW Operations - Mannually Killing a Job

6/8

Manually Killing a job

PM-03-04

Ver 1.0/14-Aug-08

Page 6 of 8

Step9: After selecting the appropriate SAP server, double click on it. Below screen will appear. From thisProcess Overview screen, search for required WP number/PID (which is 101/7.161 in this case). Here

status of the job will be running.

Step10: After selecting the required WP number/PID, click on Process tab and click on either Cancel WithCore/Cancel Without Core.

7/27/2019 FSS BW Operations - Mannually Killing a Job

7/8

Manually Killing a job

PM-03-04

Ver 1.0/14-Aug-08

Page 7 of 8

Note:Cancel with Core

Cancels the work process. A core file is created, which you can view in transaction ST11.

Cancel Without CoreCancels a work process, and a core file is not written.

Step11: After clicking on Cancel With Core /Cancel Without Core, a new pop up will appear which will askwhether to terminate the process or not ? Click on Yes.

7/27/2019 FSS BW Operations - Mannually Killing a Job

8/8

Manually Killing a job

PM-03-04

Ver 1.0/14-Aug-08

Page 8 of 8

Step12: After clicking Yes on process termination pop up, the coresponding process will disappear fromProcess Overview screen. Now you can repeat the process by right clicking the process step in process

chain and clicking on Repeat.