This content has been marked as final. Show 5 replies
Once you logout all the sessions and disable the connections, Partition will not create any issues for the restructuring.
In the BSO cube if you are building sparse dimensions, only .otl and .ind files will be restructured.
It is very fast compared to dense restructure.(.otl+.ind+.pag files will be restructured).
There is no dense/sparse concept in the ASO applications.
Any dimension building will push the cube to full restructure.
.otl and entire .dat file will be redefined.
Obviously it takes time based on the .dat file size.
Thanks for your input!!
We are still in Essbase 7.1.3!
any dimension build in ASO will cause a full restructure and will clear all the data!
so I think it is independent on .dat file!!
let me explain my issue in detail!!
lets say I'm building the XYZ application!!
I'm copying the .OTL from other application to XYZ application and on that I'm building the dimentions!!
that was our devlopment architecture!!
when I'm doing the same with BSO every thing went good!!
when I did the same thing with ASO the restructuring process is taking forever. (restructuring is being done after building every build file, the problem is only after the bilding the last file in the script).
After dropping the partitions are running again every thing is going good!!
any input? any suggestions?
Then. No issues. Define the batch flow like this:
1) Drop the partition
2) BSO cube build
3) ASO Cube build
4) Recreate the partition.
I know abt that!!
just want to know how it is affecting restructuring!!