TM1 Forum

This one is odd. We have a chore that calls upon 13 processes to execute.

The first two are control processes that call other processes to execute. They are in the chore exactly once apiece. However, when the chore runs, it, the chore, executes these 12 times before moving on the third process. Each of the first two chores executes in their entirety dutifully executing their child processes and completing.

So the execution is like this in terms of the processes in the chore: 1-2-1-2...1-2-3-4-5-6-7-8-9-10-11-12-13.

Any ideas on what could possibly cause this behavior? If we run process 1 or process 2 from their own separate chore, no problem.

The obvious option is that they are in a loop that is not behaving the way you think it should be, but without seeing your code its pretty hard to answer.

Suggest you post the code of your master chore detailing which tab each piece of code is on.

Thanks, Steve. Think we found the problem. The chore was running in single commit mode and some processes were having problems so it was constantly resetting the transaction and running again. Also, my first note was incorrect. The second control process was NOT completing. It was getting to one or two processes then the reset would occur. It was obvious looking at the server message file.

At least we THINK that is it. We're testing it now.

**UPDATE**

Be very careful using Multi Commit mode on a chore in 10.1.1. It hosed our server. We had to break the chore up into three different sections.

I also encountered this repetition of TIs. I'm not sure if it's the same with this one but, the processes got repeated so many times I had to stop it, it was really frustrating not knowing why and when they would all be done.
I certainly have no looping in this processes. As the system has been running successfully for like almost a year, until we had an issue in the ODS source.

What happened in mine is, I executed this main process (via right click->Run) that calls like 20 processes, first five let's say are for dimension updates, second five are for cubes, last 10 includes special view formatting, control TIs, and others.

This main process though is called, scheduled in a chore, but that time I just ran that process directly. So I prepared my TM1Top for duration monitoring.

Looking at the Progress Window, I noticed all my TIs started executing sequentially from dimension updates up to cube updates. Then while it was still running, a chore is registered in the TM1Top, set to execute, but on WAIT status as the main process was still running. This chore is scheduled to run every 15 minutes.

Suddenly, after a process (that was called by the main process) finished executing, I noticed that the chore that's on the WAIT, went thru processing. Executed. Done.
That's when the main process started again from the very beginning, the dimension updates.

Before I noticed this phenomenon, we re-ran the main process several times, we restarted the service several times, but this phenomenon happened over and over again, 'til I finally noticed it and decided to deactivate all scheduled chores.
Once we deactivated the chores, we then re-ran the main process. and it went thru ALL of the processes inside it successfully.

Can anyone give enlightenment on this behavior?

Thanks very much.

I too have seen this happen on occasion. It usually was due to an error in one of the processes. I didn't have time to investigate the exact conditions that make this trigger, though.

What is the commit mode your chore has?