DSXchange

Hi Gurus,
I have designed a sequencer and scheduled that sequencer at night.

Iam getting error in my sequence.Can you please help me with the techniques to handle the sequencer which has aborted at uneven times.


cheers;
Vijay

vijaykumar wrote:Hi Gurus,
I have designed a sequencer and scheduled that sequencer at night.

Iam getting error in my sequence.Can you please help me with the techniques to handle the sequencer which has aborted at uneven times.


cheers;
Vijay

What error your getting ?, send more details. :D

Any job sequence which has aborted at anytime needs to be investigated and then restarted or reset before it is run again. The answer to your question depends largely on the kind of errors you are getting.

Hi Gurus,
Actually my team lead was asking me how to handle in such cases.
I said generally we go for check points, check points acts as intermediate stopping pt which helps from failures. I wanted is there any other way to handle.

cheers;
Vijay

Hi Gurus,
Sorry i have given incomplete information. I was asking for common error handling techniques. Generally i go for only check points, are there any other ways .

cheers;
Vijay

Exception handling and re-run/re-starting of the sequences can be done in many ways. When huge data is involved and if they are stored in persistent data sets for the next step of processing in your sequence you definitely don't want to run the whole sequence again in case of errors / exceptions. You can make your main sequence keep updating a log table in your database about the proceedings of your sequences and when a error is reported you can investigate and restart the sequence by providing the step/activity where it should restart by setting a flag which identifies if it is a re-start or normal run.