Hi All,
We are trying to move the Essbase arborpath from 'PathA' to 'PathB' within the same server due to some storage related constraint. There are already some Essbase applications running under 'PathA'.
We just followed the approach below :
- Stopped Essbase and other services.
- Copied the contents of 'PathA' under 'PathB'
- Ran the following command so that config tool allows the new arborpath 'PathB' to be entered :
"./resetConfigTask.sh -product EssbaseServer -task RegisterEssbaseAsMultipleAgent"
- Reconfigured Essbase with 'PathB' as arborpath.
- Started Essbase and other services.
- Verified that new Arborpath 'PathB' is reflecting in both registry and EAS Console.
Now when I am trying to modify the old arborpath 'PathA' and startany Essbase application from EAS console, it's not starting with the following error in the application log -
Configured Disk Volume ['PathA'] does not exist.
We would like to know why Essbase is still referring to 'PathA' and where the old arborpath information is still stored ? We need to remove the entire 'PathA' to avoid any confusion and traces of old Arborpath.
Thanks,
Vishwanath