Need help with Orphaned BIBCTL jobs when DSO Activation fails

Hi Gurus & Experts,

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

Sunny