Cubeunload causes problems when TI is started from another TI

[Mark2007]

Dear all,

The question:
Is it possible, that "cubeunload" makes problems, if a TI is started from another TI?

the following situation:
I've a TI (I call it TI No 1) that imports Data from a csv-file. Every week, this TI has to run three times to get all Data for the quarter (one time per importet month). So, I designed a TI (I call it TI No 2) that calls the import-TI three times (ExecuteProcess...), e.g. for jan, feb, march.

As the RAM-usage of the server is critica, I inserted a "Cubeunload" in the Epilog of TI No 1

So, if I start TI No 1 on its own, everything is fine
If I start TI No 2, only the march-data appear in the cube

If I start TI No 1 for Jan, than for Feb, than for March, all data are available,
If I start TI No 2 again, all Data stay in the cube
(let me mention that there is a "viewzeroout" in TI No 1)

If I deactivate the "Cubeunload", everything is fine again.

TM1 10.1

Regards

Mark

[lotsaram]

Please have a look at the request for assistance guidelines and try rewording your question as it is by no means clear what you are doing, or why, or in which order. If you need help you need to do a better job of explaining what the issue is.

Which cube is being unloaded? If it is the one that you are loading data to then this is completely nonsensical!

[Steve Rowe]

Hi Mark2007

I expect you are unloading the cube before saving the changes you want are committed to disc. You want do a save data first. Not sure about the second TI. I wouldn't expect what you are trying to work under any circumstances, without a savedata.

It may also be that once you unload the cube for the first period the load is failing silently on subsequent passes (or maybe the other way round, you only get the last month). You'll need to get the cube back into RAM before doing the second and third loads by requesting a value from the cube in the prolog of your TI. Depending on the time taken to load the cube this could produce a dramatic slow down of your process.

Note though that you will only be releasing RAM back to be re-used within TM1 not back to the OS, so the total RAM consumption of TM1 won't be changed by your actions,

Cheers,

[BrianL]

In this case, I'd expect that you can get away with a CubeSaveData call to just save the cube you want to unload to disk instead of the SaveDataAll.