fss bw operations - dso activation failure

8/22/2019 FSS BW Operations - DSO Activation Failure

1/11

DSO Activation Failure due to one of the background processtermination

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

Record Of Release

VersionNo.

Created/Modified By Reviewed By Release Date Modifications Done

1.0 Sanjay / Saurabh Kush Kashyap 14/02/2011 Initial

Project ID: E6806 Project Name: FSS BW Operation


2/11

DSO Activation Failure due to the background process

termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 2 of 11

Scope of Document: This document helps us to understand the steps to be followed in case of DSOActivation Failuredue to one of the background process termination.Sample Error Message:Background process BCTL_3E3ZFGRQ2S8GHZGIE8HJYUV27 terminated dueto missing confirmation

The issue behind this problem is, during parallel activation, the child jobs acknowledge the parent jobabout status. If the child job takes long time to read data from active data table, then it times out andfails.

Step1: Log in the SAP.Enter below details:Connection Type: Custom Application serverDescription: GRPApplication server: 155.111.150.189 (we can use from 187 to 194)System ID: GRPClient: 400

Step 2: Enter user name and password.


3/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 3 of 11

Step 3: Run the transaction SA38.

Step4: Run the program /SSA/BWT.

Step 5: After clicking Execute, below screen will appear. Check the Process Chain Analysis radiobutton. Click on Execute button again.


4/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 4 of 11

Step6: Next, click on Process Chains. Below screen will appear. Enter the time and date for processchain runs. Click on execute. After execution all process chains for the given time and date selectionrange will appear.

Step 7: In the below screenshot, in the process chain GAP_GWFDAP01_GAPC0012 one of the steps hasfailed, as it is visible in the steps indicator, which has turned to red. Click on Log id of the process

chain to view in detail.


5/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 5 of 11

Step 8: Local Chain has turned to red, indicating that a step has failed inside it.

Step 9: Right Click on the failed local process chain, and then Click on Process Monitor.


6/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 6 of 11

Step 10: Process Monitor is showing DSO Activation Failure.

Step 11: Right Click on Failed DSO step, and click on Displaying Messages. It will open the logs for theprocess chain step and display the exact cause of DSO failure.


7/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 7 of 11

Step 12: Click on the Background Tab and check the messages being displayed. In this example thefailure is due to one of the background process getting terminated due to missing confirmation.

Step 13: On double clicking on the message, we are able to see the detailed description of the failure.


8/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 8 of 11

Step 14: There is also one more method to check the error during the DSO activation. Right click onFailed DSO step and then click on the Process Monitor option.


9/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 9 of 11

Step 15 : It is clear from the error analysis that the DSO activation was terminated because of abackground process getting terminated. This is probably related to the system perfromance and it is

safe to repeat the DSO Activation process again.To do so, Right click on the failed DSO step and then click on the Repeat option.

Step 16: Next a debug loop popup will come. Only use this function to debug a process run. Specifyhow long (in seconds) you want the delay to be between one event being triggered and the nextprocess starting.You can capture the process in the debugger by using transaction SM37 (Job Overview) or SM50 (ProcessOverview).


10/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 10 of 11

Step 17: The below screenshot shows that the repeat job is in progress.

Step 18: You can confirm that whether repeat job has actually started by clicking on the AdministerData Target.


11/11


termination

4PM-03-04

Ver 1.0/14-Feb-2011

Page 11 of 11

Step 19: Here under the request tab it is clearly showing the request status of DSO is Green in color,

means its activated.

Step 20: If the DSO activation fails again on the repeat attempts then escalate the issue to thePerformance Team through an incident.

fss bw operations - dso activation failure

Documents