There are several constants in our world: death, taxes, and minor Hyperion LCM tweaks with each Oracle EPM release! 22.214.171.124 is no different. Here is how to prepare for a “lift & shift” application migration from an older environment to Hyperion / Oracle EPM 126.96.36.199.
The good news is the helpful LCM features introduced in 188.8.131.52 are retained in 184.108.40.206. In particular, the ability to upload, download and delete content directly from the Shared Services Console without requiring direct access to the Life Cycle Management (LCM) file system.
If your organization has not yet upgraded to 220.127.116.11, here is a brief illustration of the helpful features we’re talking about.
LCM Download, Delete, Rename, etc.:
The trick to getting the upload to work is that the LCM artifact folder must be zipped in a particular format. You can quickly learn that format by producing an LCM export, downloading it, and then examining the zip file you receive.
Now for the bad news. The way LCM artifacts are stored on the filesystem has changed yet again.
LCM 18.104.22.168 stores artifacts on the server in a zipped format. A manual workaround is possible to keep and work with these files unzipped, but by and large you will be dealing with zipped folders.
LCM 22.214.171.124 (at least the pre-release preview in our lab) reverts to the older unzipped storage format. The directory structure is slightly different because the actual LCM artifacts are stored one level deeper than before.
Because of this difference, it is not possible at this time to directly copy LCM artifacts via the filesystem from an older Hyperion release and expect LCM 126.96.36.199 to be able to figure it out.
We have discovered two workarounds in our 188.8.131.52 lab environment that resolve this issue:
1. If your source system is 184.108.40.206, download the zipped LCM artifact to your desktop via the 220.127.116.11 Shared Services Console, and then upload it to the target system via the 18.104.22.168 Shared Services Console. 22.214.171.124 is smart enough to detect the version difference, and it will automatically unzip the 126.96.36.199 folder and and store it appropriately in 188.8.131.52’s filesystem.
2. If you have access to the 184.108.40.206 filesystem, manually create a subfolder underneath your “import_export” LCM folder. The name of this subfolder does not matter. In the example screenshot below, I named mine “220.127.116.11 Lab” to indicate that the source artifacts came from an 18.104.22.168 environment. Copy your unzipped LCM artifacts into yet another subfolder beneath this one, such as the example below.
Sound complicated? Contact us today if you’d like to explore your options on this or any other Hyperion / Oracle EPM related topic!
The “ORA-12154: TNS:could not resolve the connect identifier specified” Oracle error is a commonly seen message for database administrators.
This blog reviews how you can generate scripts for SQL server logins, role assignments, and server permissions for a smooth migration.
Our database experts explain how to recover and restore a table from an Oracle 12c RMAN Backup with this step-by-step blog. Read more.