PQ60746 4.0: Migration from V3.5.5 (or higher) to
V4.0.1 fails
Downloadable files
Abstract
Migration from WebSphere® Application Server V3.5.5 or
higher to V4.0.1 does not complete successfully.
Download Description
PQ60746 resolves the following problem:
When migrating from WebSphere Application Server V3.5.5 to V4.01 on
Solaris™, there was a problem with the migration prereq checker.
Apparently, the checker only recognizes versions up to V3.5.4. If you are
at fix pack 5 or higher, it will not detect the configuration and
therefore it will not complete successfully. The work around offered would
be to back level down to V3.5.4 and then upgrade.
LOCAL FIX:
Uninstall the current fix pack and reinstall fix pack 4. Then proceed with
the migration to V4.0.1.
USERS AFFECTED:
All WebSphere Application Server V3.5.5 Advanced edition customers
migrating to V4.0.1 Advanced or Single Server edition.
PROBLEM DESCRIPTION:
When installing WebSphere Application Server V4.0.1 AE or AEs, the
migration panel on the install GUI does not appear when V3.5.5 or a higher
V3.5 version is currently installed.
RECOMMENDATION:
If you have WebSphere Application Server V3.5.5, or a higher 3.5 version
installed, and then try to install V4.0.1, the migration panel fails to
appear. The only option is to install V4.0.1 and manually migrate from
V3.5 to V4.0.1.
PROBLEM CONCLUSION:
This problem is a result of the fact that the V4.0.1 prereq checking only
detects 3.5 versions prior to V3.5.5. The prereq.properties file was
modified to add the presently released levels of 3.5 (3.5.5 and 3.5.6)
along with higher levels that are not presently released and may never be
released. Adding these levels will allow the prereq checker to accept
V3.5.5 or higher as valid levels of the V3.5 release and cause the
migration panel to appear during a 4.0.1 GUI install.
TEMPORARY FIX:
This issue can be fixed by copying the contents of the WebSphere
Application Server V4.0.1 CD onto the local file system and then
installing the eFix. The eFix will replace the prereq.properties file. You
can not simply point to the new prereq.properties file as you normally
would for disabling the prereq checker
(./install.sh -prereqfile /tmp/prereq.properties) because the migration
code does not check the prereq file that is specified at the command line.
It always looks at the one that is in the same directory as install.sh.
The only other way to get around this issue without installing this APAR
is to go back to V3.5.4 and then run the install for V4.0.1. The installer
will then recognize V3.5.4 and prompt you for whether or not you want to
migrate.
Prerequisites
None
Installation Instructions
Please review readme for detailed installation instructions.