This content has been marked as final. Show 4 replies
You probably already know this, but let me throw it out there anyways...
If your refresh triggers a dense restructure, depending on your database size, the refresh might take long. Currently our database refresh takes almost an hour in the case of a dense restructure.
Hi Mehmet, thank you very much for your quick response.
The last changes I made to the model were adding some formulas to several sparse members, do you think it could have something to do with it (increasing refreshing time)?
As I said, the strange thing for me is that a couple of days ago, the refresh used to take no more than 2 minutes.
Adding formulas to sparse members should not cause a dense restructure... This article might give you an idea: http://www.in2hyperion.com/websites/in2hyperionblog/post/2011/01/22/Essbase-Database-Restructures.aspx
Have you checked Planning and Essbase logs?
Yeap....I've read both logs and there are no errors. Do you know the way to kill the refreshing process?