Need help with Orphaned BIBCTL jobs when DSO Activation fails

[Pepa]

Hello Gurus,

We are having this issue for the third time it has been in a row. There is a Process chain running as a part of over night job and on every Sunday it has been failing at Activation of M records for DSO and after that BIBCTL jobs are running long which does not makes any sense. It has failed in a similar way on last two Sundays.

This is error msg below :

"BCTL_DB3PWFOQB9G362CQ9VXKXXB74 terminated due to missing confirmation"

but the process keep running after that and can be killed or stopped by SM37 and SM50 and ultimately killed from Basis side.

Any help and valuable suggestion will be appreciated.

Regards,
Pepa

[Micro]

Hi Pepa,

We had a same problem happening every saturday.
The issue was non availability of background process. We have about 20 BGD processes. One full upload was taking long time (DSO Activation). When other process chain kicked offf, DSO activation was getting failed due to non availability of BGD's BI_BCTL*.
Now I just put delay of 3600 seconds on DSO activation job. Since then no failure on actavation of DSO. Check your error and if its the same case then you can put delay and test.

Regards,
Micro

[Pepa]

Hi Micro,

Thanks for your valuable comment. We have 6 background processes already but will try to increase as per your advise. Now there is a question how to put a delay of 3600 seconds on DSO activation. Can you please show me the procedure step by step?

Regards,
Pepa

[Micro]

Hi Pepa,

Go to process chain, right click on the DSO activation process and select "DEBUG LOOP", a box will be displayed "waiting time for the execution of the process" give 3600 (in seconds).

Regards,
Micro