DSO Activation Failed

8/22/2019 DSO Activation Failed

1/12

Friday, August 02, 2013L&T Infotech Proprietary

Page 1 of12

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/12


Page 2 of12

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 due tomissing confirmation

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

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/12


Page 3 of12

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 radio button.Click on Execute button again.


4/12


Page 4 of12

Step6: Next, click on Process Chains. Below screen will appear. Enter the time and date for process chainruns. Click on execute. After execution all process chains for the given time and date selection range willappear.

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/12


Page 5 of12

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/12


Page 6 of12

Step 10: Process Monitor is showing DSO Activation Failure.


7/12


Page 7 of12

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.

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


8/12


Page 8 of12

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

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


9/12


Page 9 of12

Step 15 : It is clear from the error analysis that the DSO activation was terminated because of a backgroundprocess getting terminated. This is probably related to the system perfromance and it is safe to repeat theDSO Activation process again.


10/12


Page 10 of12

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. Specify howlong (in seconds) you want the delay to be between one event being triggered and the next process starting.You can capture the process in the debugger by using transaction SM37 (Job Overview) or SM50 (ProcessOverview).

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


11/12


Page 11 of12

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


12/12


P 12 f 12

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

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

Documents

DSO Activation Failed