Hi all
I have a model which includes a TI scheduled to construct some default cube views. This has been working without problem.
I have this morning restarted the Tm1 instance and now no views are being saved.
I have also tried manually loading views (which take longer to calculate than the VMT value) but when viewing the Statsbycube cube no views are being saved.
As mentioned this was all working correctly previously.
Has anyone come across this before after a restart, or have any suggestions ?
Thanks in advance
Views not caching after restart
-
- MVP
- Posts: 1828
- Joined: Mon Dec 05, 2011 11:51 am
- OLAP Product: Cognos TM1
- Version: PA2.0 and most of the old ones
- Excel Version: All of em
- Location: Manchester, United Kingdom
- Contact:
Re: Views not caching after restart
Do you actually have performance monitoring turned on? If no the stats cubes won't update anyway.
Declan Rodger
-
- Posts: 5
- Joined: Tue Apr 21, 2015 10:26 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2010
Re: Views not caching after restart
Hideclanr wrote:Do you actually have performance monitoring turned on? If no the stats cubes won't update anyway.
Yes, I had Started the Performance Monitor while i've been looking into this.
Thanks
-
- Posts: 5
- Joined: Tue Apr 21, 2015 10:26 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2010
Re: Views not caching after restart
Hi
After reading the posts here --> http://www.tm1forum.com/viewtopic.php?f=3&t=9575 , I have this working now.
For those who have the same problem, I re-saved the main rules files on the cubes upstream of the problem cubes (forcing the re-save by making a change to the file) so the feeders are re fired.
Views are now back to being cached correctly.
After reading the posts here --> http://www.tm1forum.com/viewtopic.php?f=3&t=9575 , I have this working now.
For those who have the same problem, I re-saved the main rules files on the cubes upstream of the problem cubes (forcing the re-save by making a change to the file) so the feeders are re fired.
Views are now back to being cached correctly.
