Process chain variants suspended

[Former Member]

Hi Friends

We have daily loads through process chains and every running properly and we are on BW3.5 version.

However last night all our daily loads start variant just started and cancelled the jobs, the following variants delete index ,data load from R/3 variants not schedulled.

It's not for only one process chainl,it's happened for all process chains.Just start variant started then the next variant could not started.It's on production system.

What could be the problem?

Points will be awarded for the right answers.

Regards,

Chama.

[former_member345199 · Accepted solution]

Hi,

Can u confrim about the scheduling options?

Immediate or Periodic?

Thanks,

JituK

[Former Member · Accepted solution]

Hi

It's setup periodically.

Regards,

Chama.

[former_member345199 · Accepted solution]

Hi,

A couple of questions before moving ahead.

Is it turning into red or hanging in yellow without doing anything?

What is the error message you are getting?

Are there any other huge data loads / resource intensive activites running in parellel?

Any idea about the availability of enough BGD processes?

Thanks,

JituK

[Former Member · Accepted solution]

Hi

When we check on log on process chain maintainance screen

the start variant still shows yellow and nexet variants shows in normal not in red or yellow.

Error message says" Process DROPINDEX (variant ZPAK_37X2VVD8MQ2LOIU336IVLBOEL ) needs to be

started. According to the process chain maintenance, it needs to be scheduled while waiting for event ZPAK_37X2VVD8MQ2LOIU336IVLBOEL

9MWNI0IGZPOJ1UD0Q9H3SBGP9 . However, this is not the case.

No other huge loads happening on the box and there are 8 BGD's availlable.

But we are planning to upgrade patches to 21 as we are on 18 now.

Regards,

Chama.

[former_member345199 · Accepted solution]

Hi,

I am not sure about the cause. But we faced a similar situation. I will explain the procedure we peformed to resolve it.

Symptom: The chain is hanging in yellow state at start variant itself without going further (when it is not getting triggered / process is in yellow for a long time). If that is the case try this.

Go to Chain in Planning view.

then go to variant maintenance for the start process. (Where we schedule the chain)

Select "Start Using Metachain or API" option and save.

Come back to planning view and Trigger/Schedule the chain.

Go to Log View.

Then go to tab "view" and select "Merge active version".

Come back to Log view and right clic k(context menu) on the process which is in yellow/incorrect process. you will see a message called "Stop process again".

Click it and then refresh.

The chain should start running from where it was hanging.

Procedure for System Administration (Once the chain is over)

Steps added to put change the Process Chain back to the original stage:

1. Re-select "Direct Scheduling"

2. Re-activate and schedule the Process chain.

Thanks,

JituK

[Former Member · Accepted solution]

Hi,

coulpe of months back we faced the same kind of problem, we tried so many ways like executing the varient in SM62, force the job from release to active, but its not easy to do for all the process chains, we Re-started the server from the chains are running without any issues as per the schedules.

[Former Member · Accepted solution]

Hi

Thanks for the time and effrts.

Please could you let me know what could be the problem either patches or support pack ,system errors?

Is it occured again for you after you did the changes mentioned?.

Regards,

Chama.

[former_member345199 · Accepted solution]

Hi chama,

It occured to us only a couple of times only. we are not sure about the reasons. But it worked once we did those steps.

It is not a permanent fix, just a short term fix so that you can proceed with load.

Thanks,

JituK

[Former Member · Accepted solution]

Hi Friends

Thanks very much for you support.I have awarded the points.

Please send me the details if you find the perminent sulution and why it occured?

Regards,

Chama.

[former_member345199 · Accepted solution]

Hi,

Thanks for that nice gesture.

Will let you know when i come across a permenant solution.

Thanks,

JituK

[Former Member · Accepted solution]

Hi

Anyone has got any permenant solution to this problem.

I have followed Jitu proecedure and it did solve the problem temporary.

Regards,

Omar

[Former Member · Accepted solution]

I have the same problem in the 2004 S version. It seems like the solution mentionned above, will solve the problem temporarily, but I would also like to know if there is any good solutions on the long term.

Best Regards Ingrid