To continue.... note that the following Oracle Support documents have been referenced but, have not been tried yet: Document ID: 1366127.1, 1396937.1, 1403655.1, 1340996.1.
There are three environments, Dev,Test and, Production. ASO applications were created with no issue in the development instance. The issue is in the Test instance. The only difference that be observed is that EAS and Essbase Studio are on two different servers in the test environment versus one server in development. Again, any /thoughts/assistance/help is appreciated.
Hello again, does the Hyperion community have any ideas of what could be the issue? We are still running into an issue of crashing the environment when creating an ASO application.
Have you tried to create an application / database manually through EAS rather than going through EPMA route?
If yes, then there has to be some issue with EPMA. Are you using the same version of EPMA and Essbase ?
Hello Amarnath, did try to create the application/database in EAS and, it also crashed when creating in EAS. Same version, 126.96.36.199.
the message "Lease Manager to Initialize" point to some load balancer. I think this is the direction to look into.
I have no experience with load balancing.
Did it ever work?
If yes, what has changed?
Thank you Phillip, with one of my colleagues working through an Oracle ticket, Come to find out the essbase.sec file got corrupted. Using a "clean" essbase.sec file. We can create and ASO cube in EAS. I will update the thread once Oracle has given us a complete solution.