Activation of M records failure in DSO in process chain during weekend

[Former Member]

Hi Experts,

We have got same issue again but this time after a month's time.

Once again it happened during weekend and this is error message which is same as it was in the past : -

Error occurred while deciding partition number

PSA update failed

Process 000003 returned with errors

Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation

Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation

Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation

Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation

Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation

Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0

Log for activation request ODSR_DBA2WH3T615GA6FOR093U3W7K data package 000001...000001

Errors occured when carrying out activation

Analyze errors and activate again, if necessary

Activation of M records from DataStore object ZDSO** terminated

I have done all the things suggested by the experts but still unable to understand this strange behaviour.

Please suggest your valuable thoughts regarding how to stop this from happening.

Regards

Sunny

[former_member666794]

Looks the issue with PSA Partitioning.

Please use RSRV --> Consistency Between PSA Partitions and SAP Administration Information## to check & correct the issue.

Hope this helps.

Regards,

viresh

[former_member188080]

Hi,

Pl check all the solutions in following thread

Thanks and regards

Kiran

[Former Member]

Hi Kiran,

Thanks for your reply but i have gone through all this already

Regards

Sunny

[Former Member]

hi,

Is this issue with the same DSO or multiple DSO's, if it is the same DSO then you need to do an RSRV check on the DSO and check its consistency on the database and in case of multiple DSO's you will have to check the system resources crunch at the time of the failure.

regards,

Arvind.

[Former Member]

Hi Arvind,

I have done RSRV checks and it all seems fine there. How do you check the 'System resources crunch time at the time of failure' as you have mentioned.

Please advise me some steps.

Regards

Sunny

[Former Member]

hi,

At the time of failure check the system background processes in SM51 and see if the server has any long running jobs or may paralle jobs due to which the activation job is not getting any background process.

Please check the below thread:

You can ask you basis team to increase the number of background processes as well as the wait time for the processes to overcome this issue.

regards,

Arvind.

[Former Member]

Hi Arvind,

Thanks for your reply. Can you please advise me few things -

In RSODSO_SETTINGS -

In first option Parameter for Activation - How many No. of processes i need to set there ?

In second option Parameter for SID Generation- How many No. of processes i need to set there ?

In third option Parameter for Rollback - How many No. of processes i need to set there ?

We have DSO which has roughly 5.5 million records

Regards

Sunny

[Former Member]

hi,

Please check SAP notes and perform the activities mentioned in them

Note 118205-- RSODSO_SETTINGS Maintain runtime parameter of DataStore obj.

Note 1392715 - DSO req. activation:collective perf. problem note

regards,

Arvind

[former_member182537]

hi,

anyone found solution to this problem as in my bw system also dso activation failing from some time

i have maintained data pakcge size 50000 in RSODSO_SETTINGS

bgd process are available in system at time of activation but no clue why is it still failing

max wait time =3600

pls advice

thanks

nilesh

[Former Member]

Hi Nilesh,

We have the same issue but now is very rare but still the problem is there and that is the reason I raised this question in many ways, but to be honest none of the experts could give a firm answer on it.

We have 10000 package size and quite a lot of back ground processes and more over the time limit is also 3600. I got some links from experts which is on this forum through which you can work around your method and may be able to make your settings alot better but as i said no one could give me firm method.

Regards

Sunny

[Former Member]

Hi,

For the issue,

Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation

You should make some adjustments to the Data Store object parameters, then you should be able to activate the request.

Please make the following adjustments in transaction RSODSO_SETTINGS (you can adjust this for each DataStore object):

1) Maximum package size (for activation).

This you should reduce to 10000. Then the package processing would

be less time consuming.

2) Maximum wait time for process (for activation)

This could be increased to e.g. 600

See attached Note 1118205 for further information.

Regards,

Mani

[Former Member]

Hi Mani,

I had already done those steps you have mentioned but the problem is still occurring only at weekend but not very often, once or twice in a month.

The package size is already 10000 and activation time is 3600.

Moreover I have referred to most of the OSS notes.

Please advise me some other options.

Regards

Sunny

[Former Member]

Hi,

How many parallel process where there at the time of activation ? There may be backgroud processor unavailability ... Analyze the log and make sure that there were no special or small letters in data...

Try to activate it manually not through process chain once ....

-

---

Thanks

BVR

Edited by: binu v. rajan on Sep 20, 2011 11:12 AM

[Former Member]

HI BVR,

We have about 20 background processes and they are plenty. There is no issue related to special or small letters in data.

And yes i can always activate it manually that is not the issue, the reason of posting this thread is to resolve it forever.

Regards

Sunny

Edited by: Sunny on Sep 20, 2011 10:21 AM

[former_member182470]

Hi,

What is your Database system of BW system? Is it MS-SQL, Oracle...or something else? Generally, MS-SQL and Oracle databases will take care of their memory cleansing, releasing etc by themselves. Then the sufficient memory will alwaya be available for any jobs take place in BW system.

What is your ECC's database system?

Regards,

Suman

[Former Member]

Hi Suman,

We are using MS-SQL as our database.

Regards

Sunny

[former_member182470]

Hi,

If it is MS-SQL, please contact your BASIS team for better memory management. Cross check whether they do any automated memory cleansing mechanism? You have to coordinate with your BASIS team to ensure this problems never comes again.

Regards,

Suman

[Former Member]

Hi Suman,

Thanks for your quick response. I have checked with them and there is no problem at their end. What else can be the options to consider ? I have literally done everything, before this problem used to happen every weekend but now its on and off but still exists.

Regards

Sunny

[former_member182470]

Hi Sunny,

I also face this problem sometimes. I have got hardly two times in the last 1year. I just repeated the Process chain and proceeded successfully.

But in your case, you get every week. Although your BASIS team claims that there is no problem at their end, I strongly believe that this is a memory issue only.

There will be some periodical checks need to be done at BASIS end. As a BI Consultants, we can not do all these things.

Refer some Performance Tuning docs in SDN for your reference.

All the best!!!!!!

Regards,

Suman