DSO activation failed ..

[Former Member]

19.10.2015 04:05:02 Job started

19.10.2015 04:05:02 Step 001 started (program RSPROCESS, variant &0000006243973, user ID ALEREMOTE)

19.10.2015 04:05:02 Start process ODSACTIVAT ZPAK_3P6JWZYUC4O796P6A1OYW96BR in run 53LEV2CC0ZPWQNQGEGZIJ95SK of chain PIAM_STARTST1

19.10.2015 04:13:06 Activation of M records from DataStore object ZPM_O04 terminated

19.10.2015 04:13:06 Entire chain now has status 'R'

19.10.2015 04:13:06 Process Execute InfoPackage, variant ZIP: ZBW_OBJK_REC - Delta has status Undefined (instance )

19.10.2015 04:13:06 Process Activate DataStore Object Data, variant PIAM Activate ODS ZPM_O04 has status Undefined (instance )

19.10.2015 04:13:06 Process Update DataStore Object Data (Further Update), variant PIAM Activate Cube ZPM_C09 has status Undefined (instance )

19.10.2015 04:13:06 Process Update DataStore Object Data (Further Update), variant Generated from ODSACTIVAT ZPAK_3P6JWZYUC4O796P6A1O has status Undefined (instance )

19.10.2015 04:13:06 Process Start Process, variant PIAM Start Transactions : ISS/REC has status Completed (instance 53LEV2K0JYBM9A9WKB1UTB4IC)

19.10.2015 04:13:06 Process Execute InfoPackage, variant ZIP: ZBW_OBJK_ISS - Delta has status Successfully completed (instance REQU_53LDKE9VID6MIGO7GBL5C0J2S)

19.10.2015 04:13:06 Process Activate DataStore Object Data, variant Generated from LOADING ZPAK_3P6JWZYUC4O796P6A1OYW9 has status Ended with errors (instance ODSA_53LD74OWB2C0ZFCJKJMG1MQ

19.10.2015 04:13:06 Job finished

Hi Guys,

could you please suggest me some suggestion in this issue.........

[Former Member]

Hello Atul,

Those errors are may caused by incorrect parameter setting.

You can check the work process in T-code RZ04.

The General SAP recomendation is:

    Number of Batch processes = (All Processes/2)+1

Also you can view the Note 1392715 for more details.

   1392715  DSO req. activation:collective perf. problem note

Please reset the number of batch process and activate the DSO again.

Best regards, Andras

[Former Member]

we have applied SP17 last week after that we facing this issue...

what should i do??

[former_member183519]

Hello Atul,

Go into your DSO settings and unclick "SIDs Generation upon Activation". and then try to activate DSO .

Regards,

Hitesh

[Former Member]

Hello Atul,

This error can also be due to multiple activations running at the same time.

I hope you tried repeating the failed step?

Sadaf

[Former Member]

yes and after that it completed successfully.

[Former Member]

Hi Atul,

Are there multiple parallel activations in your chain?

If so then please make atleast one activation run after the others are done.

To me it seems more like work processes issue.

Regards,

Sadaf

[karthik_vasudevan]

Hi Atul

Could you please share the process tab in process chain log and give the details of process monitor.

There might be some additional information available there to identify the exact reason of the failure. Please share screenshots if required.

Regards

Karthik

[Former Member]

[karthik_vasudevan]

Hi Atul

The activation is successful once the step is repeated and so its clear the step failed because of unavailability of resources.

So based on all the jobs/chains scheduled during the time, you should schedule the process chains effectively, so that the jobs don't run at the same time.

If possible, you could get help from Basis to increase the resources to accommodate the scheduled jobs

Regards

Karthik

[Former Member]

no the issue is every-time i execute this chain it fails in 1st attempt and after the we applied SP17 previously it was working fine and same happening in Q and D system also.

[karthik_vasudevan]

Is it happening only with this DSO activation or all the process chains have the same issue?

Did you try to create a new variant or new process chain with this step to double check if its fails there are well? If not, would you do that now to confirm if its an issue with this DSO or the whole system.

If its related to SP17, the whole system should be affected, I believe.

Could you also please give the details of which version of SAP BW you are using.

Regards

Karthik

[Former Member]

SAP_BW

701

0017

SAPKW70117

SAP Business Warehouse

[Former Member]

and this happening only with this process chain...