TM1 Forum

Team,

We are testing one of the TM1 Rule calculation. I have modified the rule file and trying to save. It saved but when i tried to rollback the change with original rule file it sturcks(Showing NotResponding).

Trouble shoot steps:

I restarted the TM1 server services - Not worked

I also observed that *.rux$ file is generated in Data Folder. I am not sure why this file get generated.

Could you please help me to restore the orignial rule in rule editor and why this *.rux$ file get generated.

Thanks

Are you doing this in performance muddler? I would delete the $ file and try amending the rule in perspectives instead.

Team,

We are using TM1 Architect. I tried to delete the generated *.rux$ file and then restoring the rule file but still it is not responding.

Steps i did so far:

Deleted the *.rux$ file from data folder
Restarted the services
Trail 1: Restored the original rule in rule editor.
Trail 2 also i copied .rux file from QA environment to Dev environment.
TM1 architect not responding when i am trying to save.

Thanks,

I'm thinking you have a very very large feeder in your rules file and it is taking a long time to rewrite the feeders.

Team,

Yes thats true.

Feeders are placed in rule file and it is taking time.

I almost waited 3 hours but the restoration of file is not taking place.

Is there any way to disable the feeder and again enable them in backend?

Thanks

These might help,Please have a look through:

http://www.tm1forum.com/viewtopic.php?t=6764
http://www.tm1forum.com/viewtopic.php?t=3860 Thanks

Team,

Not much helpful.

My observation:

Rules i am able to save in rule editor but when i restore the feeders it hangs during saving.

Can we do some thing with feeders which can apply offline?

Thanks,

suman23479 wrote:Team,

Not much helpful.

My observation:

Rules i am able to save in rule editor but when i restore the feeders it hangs during saving.

Can we do some thing with feeders which can apply offline?

Thanks,

It doesn't "hang" as such, the server is reevaluating the feeders. Maybe it might be useful to elaborate on what the cube is and what exactly the feeders are (see the RFA guidelines) ... Chances are if the rule save is taking hours (as opposed to minutes) that the rule is significantly overfeeding. If the rule save is long and tedious but still measured in minutes rather than hours (e.g. in the 10 min to 100 min range) then depending on the model and data volume this still might be normal or expected. Once you get beyond that range to evaluate feeders then IMO there is serious over feeding or need for significant model redesign.

It is possible to attach rules independently of a client session using the RuleLoadFromFile TI function combined with a scheduled chore or tm1runti. Note that you can't just attach the feeder section or a specific rule but rather you redefine the entire rule file using the function.

Team,

I left the rule editor after saving about 10 hours. It worked.
Possible reason.
1. Huge data
2. Complex rule calculations
3. Feeder calculations.

If we want to do multiple times testing it will be not feasible.

Thanks,

It'll be the feeders.
You need to attack them from a number of angles:
a Are the feeders much larger than they need to be?
If so, fix them so they only do what they need to do.
b If they do what they should, can you conditionalise them so you control what is active (by version or similar)?
c Consider loading the data into an area which does not fire the feeders and copying it over in chunks.
If you are developing, you can prove the model logic by restricting the left hand side of the feeders down to very specific content for testing. But you still need to sort out how you are going to handle the large system you are building.

It may be worth checking whether any of the feeders are targeting consolidated cells. If so then you might benefit from reading this.

Hi Suman,

One more thing, you can check is, in logs file, how much time is consumed for feeder computation.
You can check in stats cube, to get details of how many cells are fed for that respective.

You can enable Persistent Feeders, in case you don't want server to recalc feeders (But it has it's own pro's and con's).

Regards,
Deepak Jain

Please remember to switch performace monitor onin order to view the stats.But on the whole david has extremely useful and excellent pointers to resolve your issue.Thanks