what does the planning log say ?
Are we sure that we did the changes on metadata for second cube before hitting cube refresh... is it happen all the time or is it just first occurrence?
Yes, it's pretty sure that the changes on the outline apply just once and these changes include both cubes. But as i mentioned above, we need to hit refresh twice.
It happens all the time. Nothing new for us.
Is there some sort of time out setting about it? (We don't get any timeout msgs btw.) Or any other suggestions?
Its pretty strange, Did you open SR with Oracle support for this ??
Yes I opened SR last year about it but no solution has been provided and we kinda gave up. We were suggested many steps. Here are the few ones.
Please increase the
And restart all the services and check if it works.
Please retain these values as it is.
Add the following values to the Essbase.cfg file.
Once added, You can put this on the Client as well.
These two didn't work out.
Login to EAS console > Right click on the Essbase server name
* Edit > Properties > Auto logoff
* Set Inactive limit (minutes) to 10 hours - 600 minutes
This solution has worked but it's not a possible solution obviously because of the security issues. We can't change security policy like that. Users will have 10 hours idle time? No way
4) They sugessted us to increase Planning timeout setting from 1 hour to 4 hours by editing web.xml file. It's been set but no luck on that too.
That's a summary of our SR and their suggestions.
If EAS solution of 10 hours works..Then I think you have a huge planning cube.
As a work around can you split the cube. Like histroy data on one cube and cube B have all the data of last 2 years.
This might help, as much i think