Essbase in EPM Planning 11.2.14 to .15 in-place upgrade looking for best practice hints
Looking for experience reports of where you upgraded a live Production EPM system with Planning/Essbase of pre-11.2.15 to .15 (i.e. to 21c) and then further to latest version, where LARGE Essbase cubes are involved. Due to recent experience at multiple systems where the conversion of Essbase during ConfigTool took many hours and had disk space issues. Although the readme .15 mentions that 2 times as much space as EssbaseData is required on Essbase server in MiddlewareHome folder, plus 1 times as much space also in user TEMP folder.
You can then run into further problems as the Essbase Config finally zips up the output for the complete Planning app (including the Essb.export of all data) and tries to place this in LCM share on the Foundation Web server (where LCM artifact migration folder defined) and - further disk space issues on Web server may occur - plus the LCM can't be uploaded as the structure of that zip file is different from normal EPM LCM packages. Apparently the items in the Essbase/Planning app's zip generated at end of the .15 Essbase upgrade configtool process, is prepared for 21c