Cubes not feeding on server start-up

[MattDavis]

Hi all

is there a way to force TM1 to generate feeders in a certain cube order, when restarting the server?

we are using 9.4.0 and helpfully the order that feeders are computed are displayed in the message log. I'd never normally consider the cube order a problem as in previous versions of TM1(9.1 and 8.4.3) it hasn't been an issue (certainly in our models anyway) - however after startup we have output cubes with some unfed data in.

To correct it I have to manually generate the feeders by the old "space bar - rule save" method, and then all data comes through correctly.

as an example: three particular cube are an issue. I need TM1 to generate feeders in this order..

Raw Data cube => Mapping cube => Output cube

but I can see from the server message log that TM1 generates feeders in this order..

1. Mapping cube
2. Output cube
3. Raw Data cube

as I said above this in turn is leading to unfed data in the Output cube

please help!

Matt

[jim wood]

If I remeber rightly there is a setting in the CFG file where you force this to happen. I'm certain this is the case for 9.4. You might want to check the admin guide. (Or whatever they are calling it these days.)

[lotsaram]

Your issue is not a common one but not unheard of. Cubes always seem to load in a predefined order, you could play around with the cube names to get them to load in the desired order, but in an established system this is probably not an option due to the rework required.

As event triggered chores/processes do not yet exist a possible solution would be to:
Have a chore scheduled at a very regular interval (say 5 minutes) that
- checks the value of a consolidated cell in the "output" cube that you know is not fed on server load
- if the value is non-zero then exit process
- if the value is zero then
- reprocess feeders for raw data
- reprocess feeders for mapping cube
- reprocess feeders for output cube