Using savedataall in a TI process I got this message in the progress box.
Completing Could not write dimension definition to disk storage procedure of process _make_view
Does anyone know if this is a spurious message as the TI process went on and completed successfully. _make_view.pro did save with changes.
Any help received with thanks.
Regards
John
savedataall: Could not write dimension definition to disk
-
- Community Contributor
- Posts: 300
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
- paulsimon
- MVP
- Posts: 808
- Joined: Sat Sep 03, 2011 11:10 pm
- OLAP Product: TM1
- Version: PA 2.0.5
- Excel Version: 2016
- Contact:
Re: savedataall: Could not write dimension definition to dis
John
I haven't seen that specific message but I have seen a lot like it. It is probably spurious. What version are you on? We used to get this a lot in 9.1, but I don't think I have seen it in 9.4 or 9.5.
Regards
Paul Simon
I haven't seen that specific message but I have seen a lot like it. It is probably spurious. What version are you on? We used to get this a lot in 9.1, but I don't think I have seen it in 9.4 or 9.5.
Regards
Paul Simon
-
- Community Contributor
- Posts: 300
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: savedataall: Could not write dimension definition to dis
Thanks Paul. I am on 9.4.1
The issue seems to be something to do with this
http://forums.olapforums.com/viewtopic. ... 531#p11949
The issue seems to be something to do with this
http://forums.olapforums.com/viewtopic. ... 531#p11949
When I run savedataall on its own there are no problems.Per a recent exchange I had with support, SaveDataAll has to be in a process all by itself in a chore by itself. This is an artifact of the new locking scheme (why, I have no idea). Leaving SaveDataAll as part of other processes or in chores can result in a Rollback loop. I scrubbed all of them out of my processes and chores and replaced them with a single one that runs nightly.
On a related note, the new locking scheme also seems to have problems with overlapping chores. My guess is they're being over-conservative (or have a bug in) their collision detection algorithms.