Exporting Cubes/Views

[par3]

Hy Guys,

I would just like to know if there are a file size limit to what can be exported in TM1? I am trying to export a view and then reload it in TI but in the final result there are data missing. Anybody have any ideas?

Thanx!

[Martin Ingram]

Is there data missing in the file you've exported, or data missing in what you've reloaded - may be that you have lines of data with duplicated element combinations - if so, you need to make sure that you have the 'Accumulate Values' option ticked in the TI process you're using to load the data back in with.

[John Hobson]

Par3 - what version are you using?

We are using 9.1.3 and are currently investigating an export / import that did not work as expected. When we looked that the exported file that does not seem to have exported all the expected data.

I'll report back with what we find.

[Martin Ingram]

I seem to recall an issue where rules calculated values that weren't being properly fed, were missing from an asciioutput?

[David Usherwood]

They would be (excluded). Unfed numbers fall out of zero suppression.
par3, you might try sending the result from a view directly to the destination rather than via a file. Don't think it'll work round the issue (probably) but would be neater.

[par3]

Guys,

I am using 9.1 Sp3. It seems that some of the data has gone missing when exporting. When however I export them with one element at a time from a dimension all the records are exported.

The reason I am using this method to load my cube is because when you run a TI using the view as data source it once took more than 8 hours!!! I am considering getting rid of this method so I need an alternative. Any other ideas maybe?

[Steve Rowe]

Not sure if it is practical for you but,

I would test on a release other than 9.1
Rasie with Cognos to see if it is a known issue.

Some more questions about what you are doing...

Are you exporting input numbers or ruled values or consolidated values?
How are you exporting the view, via TI or via the server explorer using right click, export as ASCII?
How are defining the view you are exporting, by the export as ASCII editor or a view saved as a cube viewer?

If you are taking 8 hours to export a view from 1 cube to another then there's only a few options I think.
1. Massive user error.
2. You are on a dodgy release.
3. Very strange / broken design.

Seems to be some fairly strong hints that it's No 2. (<---See what I did there )

In terms of getting cube to cube exports runnng faster when you are having speed issues what can work well is splitting the source cube up into chunks.
For example if you are exporting a whole year of data and to calculate that whole year of data takes TM1 a long time, what I have found to have a large effect on performance is to export the view but just a month at a time. This fairly easy to do within a while loop in the prolog of the TI. TM1 will construct the entire source view in memory before it begns to process it, so by processing only a 12th of the data 12 times you get a performance gain. I know this doesn't make that much sense but I guess there is an overhead to creating a large view that doesn't exist when creating a small view.

Sorry this ain't much help.

[George Regateiro]

This was an issue with 9.1. We experienced this in 9.1 SP2 and was under the impression that it was corrected in SP3, but I guess that was not the case. We had a view that started to hang on exporting. Logged it with their support about a year ago. Like I said thought from my communications with support that it had been fixed in one of the other releases. They closed my inquiry since they already knew about it.