This content has been marked as final. Show 6 replies
Apparently it is not supported and LCM require both the source and destination environments to be of the same version.
It may all work or just certain components migrate successfully, also LCM does not support essbase studio yet.
In that case, would it require a Database restore for EPMA, Planning and Essbase Studio?
For Essbase Hope I can create a blank application and move the .otl files and calc scripts and data(Level 0 Export, Import and Agg).
For FR and Web analysis, Hope the reports can be exported and Imported.
Also would like to know if there is any documentation for migrating from 18.104.22.168 to 22.214.171.124.
For shared services do we have to migrate the data from 126.96.36.199 to 188.8.131.52 using HSSMigrate.bat?
Any help is appreciated.
LCM migrations can take place from 184.108.40.206 to 220.127.116.11 . YOu just need change the folder structure bit of the 18.104.22.168 and add a import and export xml file. The format of the xml files can be obtained by taking a test lcm backup from 22.214.171.124 environment.
But you will face issues with Business rules. You need to export the business rules for calc manager as 126.96.36.199 does not have business rules.
Hope this helps.
Edited by: Saurav Sarkar on 4 Dec, 2012 1:52 AM
Oracle says we have to install 188.8.131.52 on the new servers. Use LCM to migrate the applications from old to new server and then apply 184.108.40.206 as a maintenance release. Is this the recommended path to upgrade from 220.127.116.11 to 18.104.22.168? Just wanted to make sure.
What you described is the supported upgrade path.
Sometimes you can find other creative ways to migrate the objects depending on what you need migrated - but LCM is not supported between two different versions so you can't use that.