This content has been marked as final. Show 6 replies
If you want to migrate the outline then that is possible, the copy/paste functionality for members/hierarchies is not available in ASO.
You could try to extract the information from the source database and load it to the target database with a load rule, or get hold of the metadata which loaded the hierarchies to the source database and reuse it.
It does seem possible to copy and paste members and hierarchies from one outline to another in ASO and in fact we do it every now and then. We do it through EAS interface - open both the outlines in Edit mode and copy from one and paste into another.
I also sometimes faced the issue which Auron is facing - it would just hang and not proceed. It generally happened when trying to copy-paste large hierarchies (100,000+ members). I was able to make it work by using local EAS console and not web one. Sometimes i had to even compress the outline.
This is on version 184.108.40.206
Sorry you are correct, I was thinking about copying between BSO <> ASO outlines and plus I shouldnt trust what I read in posts - Unable to paste dimension from one Essbase ASO outline to another :)
The amount you can copy is possibly down to the amount of memory available.
I think Sunil has the right answer for you. I've found if I'm trying to copy a really large dimension, I have to break it up into pieces. I'll manually create the top members then copy and paste sections at a time to get it to work. Rember, you can only copy like outlines Aso to ASO BSO to BSO.
The other way I like doing it is to use the outline extractor from Applied OLAP (free download) and export the dimension and then import it into the new outline
1. Connect to ASO cube thru Excel and retrieve required members...
2. Copy the members into Text file and save.
3. Build the dimension using rule file (Genref,levelzero or Parent/child)
this will be easy..
Yeah, the guy that answered that post...dodgy. :)
Glenn, as always, is right. It's the copy between BSO and ASO that doesn't work. My mistake and sorry for the misinformation.