Does anyone know where this message comes from:
Within the TI process message box this flashes up:
"Could not write Dimension Definition to disk storage"
This is in a TI process that issues a processexecute to several other procs. The display in the TI process running shows the progress through each of the processes called and then prior to the final process flashes up this message and then goes to process completed OK.
Originally I thought this was down to the disk on the server being full, but I have cleared the server disk space and restarted the server and this message still persists. It does not seem to be a problem but if anyone has an explanation I would be eternally grateful.
Regards
John
Could not write Dimension Definition to disk storage
-
- 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
- Steve Rowe
- Site Admin
- Posts: 2456
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Could not write Dimension Definition to disk storage
Hi John,
I don't know the answer to this John, but you might want to look at the data sources of your processes. You might find that one of the prior processes has a lock of some kind on the dimension when you try and change it. I know that at one time ExecuteProcess caused significant issues when it used TM1 objects as data sources and then later in the sequence of TIs that object was changed.
The usual workaround was to ASCIIOutput the TM1 object and then use that file as the datasource.
Not sure if this helps with your issue or not...
Cheers
I don't know the answer to this John, but you might want to look at the data sources of your processes. You might find that one of the prior processes has a lock of some kind on the dimension when you try and change it. I know that at one time ExecuteProcess caused significant issues when it used TM1 objects as data sources and then later in the sequence of TIs that object was changed.
The usual workaround was to ASCIIOutput the TM1 object and then use that file as the datasource.
Not sure if this helps with your issue or not...
Cheers
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- 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: Could not write Dimension Definition to disk storage
Hi Steve
Thanks for your reply. This does help. However my TI processes are not modifying a user dimension so I would think that this would be a TM1 internal dimension - something to do with the performance stats set up.
Will keep plugging till I find an answer.
Thanks for your reply. This does help. However my TI processes are not modifying a user dimension so I would think that this would be a TM1 internal dimension - something to do with the performance stats set up.
Will keep plugging till I find an answer.
- 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: Could not write Dimension Definition to disk storage
John
I saw this today 9.4 MR1 FP2 HF16 for the first time. Admittedly I was running someone else's code so I couldn't say whether it was doing anything unusual.
Does your message come up in the progress box while the TI is running?
Having said that it didn't seem to cause a problem, so it may be a spurious message. If you see it again I would check the Data Directory to verify that the dimension .dim file has been updated. If you have an old .dim and a .dim$ then there really is a problem.
Regards
Paul
I saw this today 9.4 MR1 FP2 HF16 for the first time. Admittedly I was running someone else's code so I couldn't say whether it was doing anything unusual.
Does your message come up in the progress box while the TI is running?
Having said that it didn't seem to cause a problem, so it may be a spurious message. If you see it again I would check the Data Directory to verify that the dimension .dim file has been updated. If you have an old .dim and a .dim$ then there really is a problem.
Regards
Paul
-
- Community Contributor
- Posts: 139
- Joined: Mon Sep 15, 2008 1:45 pm
Re: Could not write Dimension Definition to disk storage
Hi,
I haven't seen your particular message yet, but in general I pay little attention to the messages in the progress box. (Except for the last one that says executed succesfully or not).
I.e. I have never determined why exactly but in my experience the messages in there are rubbish half of the times anyways. I see names of unrelated processes aso all the time in there and this has been the case for years over afaik all TM1 releases.
Jeroen
I haven't seen your particular message yet, but in general I pay little attention to the messages in the progress box. (Except for the last one that says executed succesfully or not).
I.e. I have never determined why exactly but in my experience the messages in there are rubbish half of the times anyways. I see names of unrelated processes aso all the time in there and this has been the case for years over afaik all TM1 releases.
Jeroen