The Performance Architects team recently built an automated Lifecycle Management (LCM) refresh process for one of our clients that exports out Oracle EPM artifacts from a source environment, copies them over to the target using Secure Copy Protocol (SCP), and imports them into the target using Oracle’s Lifecycle Management utility. While testing this process, we identified a limitation where an LCM ZIP file is not created if the file size exceeds a certain threshold value. Although this is not a very common issue, it can be frustrating to deal with if you don’t know what to look for to fix it. This blog post intends to provide step-by-step guidance on fixing this issue.
When running an LCM export, the process creates a ZIP file as expected. As the ZIP file size exceeds the threshold, while the export is running, it converts the ZIP into a directory in the same location. This threshold value is set to 1.8GB and can be found under “zip.threshold” (maximum ZIP file threshold size) property in “Shared Services Deployment Metadata”. The challenge with LCM creating a directory instead of a ZIP file is that the contents of this directory will have to be manually zipped up in the correct format so that it can be used on the target environment for an LCM import.
To update the “zip.threshold” property, navigate to the “Shared Services Console” and expand “Application Groups > Foundation > Deployment Metadata.”
In the “Artifact List” window, expand “Shared Services Registry > Foundation Services > Shared Services.” Right click on “Properties,” and select “Export for Edit.”
Save the “Component.properties” file to your local drive and edit it using a text editor of choice. You will see the “zip.threshold” set to 1.8 (this is the default value in GB).
Adjust this value to suit your current needs. Save this file and import the edited “Component.properties” file by using “Import after Edit” option.
Make sure to restart “Shared Services” for the new property value to take effect!
Note: Oracle documentation mentions the default and optimal value for this property to be 1.8 GB. Any size bigger than this, may result in browser and JDK limitations for ZIP and download.
If you want to avoid changing the “reg.properties” value, a different approach is to write a piece of code that will manually create the ZIP file after LCM export is complete. The idea is to use shell or batch script commands to check for the folder name which gets created as part of the automated LCM process, and then zip up the contents into a ZIP file in the format appropriate for LCM import.
What are some ways that you have solved this issue? Let us know in the comments below! If you’re interested in learning more, click here to send us an email.