7 replies to this topic

[Talken38]

Hello,

we are moving or migratinf our dollar universes production nodes to another new machines, and everything seems to works fine.

But I have made a mistake, and ERASE all the planifications from these nodes, because I dont want to execute nothing from the tasks that we have migrated. These nodes are not in prodcution yet

When I have erased all the calculated taks, I stop the calculator and launcher engines, and make my proves, and everithig works.

But when I have started the calculator engine again, only calculates from the point time that I have erased, a few hours later, and then the xalculator engines only calculates tasks from the future, but the deleted planifications never more are calculated.

With proceses that execute day by day, no problem, we migrate on 10 days, so they are going to be calculated tomorrow again.

The problem is with the month tasks, semanal, etc.

The point I want to reach: is there anything we can do to "recalculate" everything from a point in the time from the past, for example, today at 10:00 AM????

Thanks for your help, really need.

[GCE]

Hello,

Unfortunately, this is not possible unless you change the system time and date.

However, I suggest that when you insert your items on the new servers ( not live yet) you insert your task as models.

To make your new servers lives servers you'll just have to distribute your task to the proper management unit, therefore all tasks will be calculated to populate the future launch for the next day or the nex month.

Hope it helps.

[Talken38]

OK then, you can close post.

I have tryied this, to open an existing task, modify something and then leave it as I have opened it and then SAVE the task without changing nothing, and it forces to recalculate the task. It works ok.

I have to do it with all the mensual and annual tasks, but that solves the problem.

Thanks so much.

Moisés

GCE, on April 13 2010, 02:06 PM, said:

Hello,

Unfortunately, this is not possible unless you change the system time and date.

However, I suggest that when you insert your items on the new servers ( not live yet) you insert your task as models.

To make your new servers lives servers you'll just have to distribute your task to the proper management unit, therefore all tasks will be calculated to populate the future launch for the next day or the nex month.

Hope it helps.

[men]

Hi,

One thing you may also try - if I'm not arriving too late - is to update the General Calendar (force a change in the far future, like changing a day type, then revert the change): This should force recalculation of all Tasks - from the present time.

Michel

[Talken38]

men, on April 13 2010, 05:39 PM, said:

Hi,

One thing you may also try - if I'm not arriving too late - is to update the General Calendar (force a change in the far future, like changing a day type, then revert the change): This should force recalculation of all Tasks - from the present time.

Michel

Thats even more better. Fantastic solution, thats what I was looking for. Thanks so much.

Michel, thanks so much, fantastic work.

[men]

Happy and blushing

[Silverdollar]

Had an issue in v5.2.3 patch FX24520. Transferring tasks from Integration to Production area made the tasks jump to the next scheduled day rather than the current (missing a launch). Doing this as removing the integration area and making the production the default $U operating area.

A large amount of tasks were involved and manually updating them would take a long time and would be prone to errors.

After transferring the tasks, a day in the calendar, in the future, was changed from a work day to a holiday. This was confirmed then changed back causing all the transferred tasks to recalculate themselves to the correct launch dates. Saved a lot of problems and time.

Think this fix should be added to the knowledge base as this is a very usedful technique. May not be an issue at higher patch levels though.

Edited by Silverdollar, 13 April 2011 - 02:02 PM.

[Talken38]

Silverdollar, on April 13 2011, 02:00 PM, said:

Had an issue in v5.2.3 patch FX24520. Transferring tasks from Integration to Production area made the tasks jump to the next scheduled day rather than the current (missing a launch). Doing this as removing the integration area and making the production the default $U operating area.

A large amount of tasks were involved and manually updating them would take a long time and would be prone to errors.

After transferring the tasks, a day in the calendar, in the future, was changed from a work day to a holiday. This was confirmed then changed back causing all the transferred tasks to recalculate themselves to the correct launch dates. Saved a lot of problems and time.

Think this fix should be added to the knowledge base as this is a very usedful technique. May not be an issue at higher patch levels though.

Very interesting ... thanks so much ...