JohnGoodwin wrote:I donot know what to decide. Since I have both options(One is to let them replicate the system and the other is to do a fresh install) open right now, What do you think is the best approach we take keeping in mind we still need to have both the systems up and running atleast for a temporary period to do the migration.
As it is Linux then it is possible if it is a replica, if the host name is going to be different then you won't be able just to start to Essbase as it will already be configured against the original host.
Going to leave it there as some think Windows works the same as Linux :)
JohnGoodwin wrote:One last question please, When you say you can "keep them seperate" do you mean I can configure against a new shared services? Please clarify. Please.
If you going down the new installation of Essbase route then you can point to the existing Shared Services and add a new Essbase instance or you can keep them separate, whatever route you will be able to migrate the current applications. Anyway that is enough from me hope it is successful.
Teddd wrote:If you want to use a separate Shared Services then it is possible, the choice is yours which route you want to take.
One last question please, When you say you can "keep them seperate" do you mean I can configure against a new shared services? Please clarify. Please.
The only way we by-passed this issue was by installing and configuring essbase from scratch on a new server as Our Linux group could not downgrade the glibc to a supported lower version. Oracle's response was to upgrade(BTW which version are you on?). I guess the one good thing going for me was it happened on dev first. Hope this info helps. Good Luck.