Essbase Maintenance and copying applications

Question

Good Morning
My question is in two parts. We are using Essbase version 11, ASO cubes
1) Is it ok to perform maintenance on your cubes while users are in the system? Reason I ask is that there have been times when changes need to be made right away, during the day, when the system is being utilized. If not, what is the optimal environment for making changes (adding an element to a dimension etc)
2) As part of our monthly maintenance - we normally create a copy of a cube, make changes to the copy, delete the original and copy the back up back
For example. I will have a cube called "REPORTING". I will make a copy of this and call it "BACKUP". I will then make the changes to "BACKUP". Once these are complete, I will delete the "REPORTING" cube, then I will copy the "BACKUP" cube and call it "REPORTING". This allows me to make changes with minimal delay to users. However, lately, when copying the cube I have been getting the following error message:
Cannot open object file: E:\Hyperion\products\Essbase\EssbaseServer\app\REPORTING\log\ess00001.dat
Failed to copy application [BACKUP]
The system will not longer allow me to copy the backup cube and call it REPORTING. It will let me copy it if I give it another name
Is my continual copying and deleting of applications ok? Or will it eventually corrupt the databases?
thanks as always for your expert opinions

Answer 1

user3055639 wrote:
Good Morning
My question is in two parts. We are using Essbase version 11, ASO cubes
1) Is it ok to perform maintenance on your cubes while users are in the system? Reason I ask is that there have been times when changes need to be made right away, during the day, when the system is being utilized. If not, what is the optimal environment for making changes (adding an element to a dimension etc)In an ASO cube, you can delete and load slices of data without inturrupting user activity, but if you are making changes to the outline, users have to be off of the cube. Essbase will not let you restructure if there are active users on the cube
>
2) As part of our monthly maintenance - we normally create a copy of a cube, make changes to the copy, delete the original and copy the back up back
For example. I will have a cube called "REPORTING". I will make a copy of this and call it "BACKUP". I will then make the changes to "BACKUP". Once these are complete, I will delete the "REPORTING" cube, then I will copy the "BACKUP" cube and call it "REPORTING". This allows me to make changes with minimal delay to users. However, lately, when copying the cube I have been getting the following error message:
Cannot open object file: E:\Hyperion\products\Essbase\EssbaseServer\app\REPORTING\log\ess00001.dat
Failed to copy application [BACKUP]
The system will not longer allow me to copy the backup cube and call it REPORTING. It will let me copy it if I give it another name
Is my continual copying and deleting of applications ok? Or will it eventually corrupt the databases?
thanks as always for your expert opinionsI guess it depends on how you do the copies. What you describe is something that is done often. It soulnds like something got messed up in the copy. you could try stippong the apps and copying the file from the backup to the reporting app manually. The one thing can you lose by doing what you are is security.