CRIMA1020E: Installation Manager Throws Error While Applying WAS Fixpack v8.5.5.12 !!!
While upgrading WAS to fixpack 8.5.5.12, Installation Manager throws many CRIMA1020E errors. Some of the errors are mentioned below in the failed upgrade logs:
Error during "install" phase:
CRIMA1020E: Failed to extract zip
com.ibm.websphere.ND.ndonly_027_all.all 8.5.5012.201706271504. File
/apps/app/IBM/WebSphere/AppServer/properties/messages/en/com.ibm.datapow
er.dmi.messages.xml already exists.
Explanation: A compressed file was not extracted because the
extraction will overwrite an existing file. An issue has occurred with
the package that cannot be resolved by Installation Manager.
User Action: Identify the package that has the issue. Contact IBM
Support.
CRIMA1020E: Failed to extract zip
com.ibm.websphere.ND.ndonly_027_all.all 8.5.5010.201607210521. File
/apps/app/IBM/WebSphere/AppServer/properties/messages/en/com.ibm.datapow
er.dmi.messages.xml already exists.
Explanation: A compressed file was not extracted because the
extraction will overwrite an existing file. An issue has occurred with
the package that cannot be resolved by Installation Manager.
User Action: Identify the package that has the issue. Contact IBM
Support.
CRIMA1020E: Failed to extract zip
com.ibm.websphere.ND.ndonly_036_dist.all 8.5.5010.201607210521. File
/apps/app/IBM/WebSphere/AppServer/profileTemplates/cell/default/document
s/config/templates/system/jdbc-resource-provider-templates.xml already
exists.
~~~ many other CRIMA1020E error messages with different file names ~~~
If you proceed deleting the referred files names in the log file, it's very likely that you will be presented with new set of referenced files with similar error.
This error is tricky and generally points to IM Agent Data/IMShared Data Corrupted or WebSphere Install files are corrupted (WAS_HOME/properties/version/installed.xml ~ corrupted and related files missing)
Following are the few points which can be tried to resolve this error:
1) If the customer has a back up of the initial 8.5.5.10 WAS installation, IM agent data, and IMShared location, prior to upgrade, they can restore the current directories from the back up and try again.
2) Script can be created to remove the referenced files that IM was complaining about. Please follow the below steps to run the script and try updating to 8.5.5.12.
Note: No guarantee that this script will work and allow the 8.5.5.12 update to be successful, since the IM agent data is corrupted. IM may or may not complain about other files, after running the script.
2.1) Backup the WAS installation location
2.2) Custom delete script <delete_script> placed in appropriate location
2.3) Give the appropriate permissions: chmod 775 <delete_script>
2.4) Run the script
2.5) Make sure the files and directories inside <delete_script> are removed.
2.6) Try updating from WAS ND 8.5.5.10 to WAS ND 8.5.5.12 again.
3) If the customer has a similar sister system, as the affected system, they can try installing the same versions of IM, WAS 8.5.5.10, Java7, Java8 on that system using the same directories as the affected system (including the IM agent data and IMShared locations). They can copy over and replace the directories to the affected system (WAS installation location, IM agent data, IMShared) and then try updating to 8.5.5.12 on the affected system. As an alternative, they can try updating to 8.5.5.12 on the sister system, and then copy over the above directories, so they would not need to perform the update on the affected system.
4) If all the above options fail or is not an option for the customer, unfortunately, the customer would have to uninstall and re-install WAS on the affected system, to recover from the corruption.
I have tried and tested step - 1/3 and it has worked in multiple environments. In case it does not work, then last option would be to proceed with clean-up and re-install of the product which can be complex task.
More information about IM Agent Data and IMShared folder, please visit link:
Happy Resolution !!!
In case of any questions/help - Please update comments !!!
Comments
Post a Comment