There are several constants in our world: death, taxes, and minor Hyperion LCM tweaks with each Oracle EPM release! 188.8.131.52 is no different. Here is how to prepare for a “lift & shift” application migration from an older environment to Hyperion / Oracle EPM 184.108.40.206.
The good news is the helpful LCM features introduced in 220.127.116.11 are retained in 18.104.22.168. 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 22.214.171.124, 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 126.96.36.199 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 188.8.131.52 (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 184.108.40.206 to be able to figure it out.
We have discovered two workarounds in our 220.127.116.11 lab environment that resolve this issue:
1. If your source system is 18.104.22.168, download the zipped LCM artifact to your desktop via the 22.214.171.124 Shared Services Console, and then upload it to the target system via the 126.96.36.199 Shared Services Console. 188.8.131.52 is smart enough to detect the version difference, and it will automatically unzip the 184.108.40.206 folder and and store it appropriately in 220.127.116.11’s filesystem.
2. If you have access to the 18.104.22.168 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 “22.214.171.124 Lab” to indicate that the source artifacts came from an 126.96.36.199 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!
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.