CRIMA1020E errors when updating WebSphere Portal v8
In the on-screen output and the IBM Installation Manager logs, you may see an error similar to the following:
CRIMA1020E: Failed to extract zip wp.db.impl 126.96.36.199209261939. File /opt/IBM/WebSphere/PortalServer/base/wp.db.impl/config/includes/wp.pcm_tasks.xml already exists.
The error occurs when the IBM Installation Manager has become corrupted. More often than not, this is a result of a previous upgrade attempt that failed, and either did not rollback cleanly or did not rollback at all. This can be confirmed by reviewing the <IIM Data>/histories for IBM WebSphere Portal Server and noting any "INCOMPLETE" upgrade attempts. For reference, the IIM Data directory default locations are:
Windows: C:/Program Data/IBM/InstallationManager
Linux/UNIX (root): /var/ibm/InstallationManager
Linux/UNIX (non-root): /home/<user id>/var/ibm/InstallationManager
Another cause is trying to use multiple installations of IBM Installation Manager (an admin installation and a non-admin installation for example) to manage the same packages. This is generally not recommended.
Resolving the problem
To resolve the problem, the easiest and quickest method is to restore a backup of the IIM Data directory, if available.
If a backup is not available, there are two options:
Option 1: If you have another environment installed elsewhere, it is possible to take its IIM Data directory and copy it over to the broken environment. However, certain conditions must be met:
- The exact same packages at the exact same levels must be installed. If your broken environment has WAS v8005, Portal v8000 CF3, and IHS v8000 installed, then the 'working' environment must also have the same packages installed.
- Must be the same operating system
- Alterations will need to be made to the installregistry.xml and installed.xml files to account for environmental changes, like hostname and user credentials.
It is strongly recommended that should you decide to proceed with this option, you contact IBM support for assistance.
Option 2: Delete the files that IIM complains about, and re-launch the installation. This method will work but is very very tedious. You will most likely find that each re-attempt of the installation yields different files that "already exist", causing you to have to repeat this process multiple times before getting it to go through. To make this process go a little quicker, you can take these steps to skip the credential validation that happens during the upgrade:
- Edit the <IIM root>/eclipse/configuration/config.ini file
- Add the following line to the file (make sure there are NO BLANK SPACES at the end of the line):
- Save the file.
You may also examine this log:
to see if it contains additional files to delete that may not have been displayed in IIM. Note that ".metadata" is a hidden directory, and ".log" is a hidden file.
At the time of this writing, it is not possible to simply overwrite the existing files.