Today I accidentally created a new EPM 11.1.2.4 Essbase instance with the wrong ARBORPATH. Strangely enough I discovered that the EPM Configuration Tool doesn't allow to change the ARBORPATH. This seems to be the default behavior since EPM 11.1.2.3.
Luckily there is an easy fix: Simple reset the Essbase agent configuration task, and you are able to edit the ARBORPATH value in the EPM Configuration Tool.
Open a Windows command prompt and navigate to "%EPM_ORACLE_HOME%\..\user_projects\epmsystem<x>\bin" where <x> must replaced by the digit matching your environment. Execute the command below:
Afterwards you can start the EPM Configuration Utility and change the ARBORPATH value.
Source: Wrong ARBORPATH on Essbase Instance (Doc ID 1910743.1)
Luckily there is an easy fix: Simple reset the Essbase agent configuration task, and you are able to edit the ARBORPATH value in the EPM Configuration Tool.
Open a Windows command prompt and navigate to "%EPM_ORACLE_HOME%\..\user_projects\epmsystem<x>\bin" where <x> must replaced by the digit matching your environment. Execute the command below:
Afterwards you can start the EPM Configuration Utility and change the ARBORPATH value.
Source: Wrong ARBORPATH on Essbase Instance (Doc ID 1910743.1)