Fixes are available
PM15531; 7.0.0.9: errors occur during migration from 5.1 to 7.0.0.9 on iSeries
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
While migrating WebSphere Application Server V5.1 to V7.0.0.9 on iSeries 5.4, migration fails with errors: com.ibm.ws.migration .utility,upgrade exception: could not find java_home path for was release: -------------------------------------------------------------- MIGR0201I: The migration function initialized log file WASPreUpgrade.log. MIGR0300I: The migration function is starting to save the existing Application Server environment. MIGR0302I: The existing files are being saved. Could not find JAVA_HOME path for WAS release: BASE com.ibm.ws.migration.utility.UpgradeException: Could not find JAVA_HOME path for WAS release: BASE at com.ibm.ws.migration.common.ISeriesInfo.fetchSetupSettings(ISeri esInfo.j ava:267) at com.ibm.ws.migration.common.DefaultOSInfo.configRoot(DefaultOSIn fo.java: 431) at com.ibm.ws.migration.preupgrade.R50BackupFiles.baseBackupFiles(R 50Backup Files.java:108) at com.ibm.ws.migration.preupgrade.DefaultBackupFiles.createTransfo rmMappin gs(DefaultBackupFiles.java:97) at com.ibm.ws.migration.preupgrade.DefaultBackupFiles.<init>(Defaul tBackupF iles.java:59) at com.ibm.ws.migration.preupgrade.PreUpgradeTransformProviderImpl. provideD efaultTransforms(PreUpgradeTransformProviderImpl.java:139) at com.ibm.ws.migration.preupgrade.PreUpgradeTransformProviderImpl. provideD efaultApplicationServerTransforms(PreUpgradeTransformProviderImp l.java:1 17) ================================================================
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users migrating to IBM WebSphere * * Application Server V7 from V5.1 on iSeries * **************************************************************** * PROBLEM DESCRIPTION: The WASPostUpgrade process exits * * early, as it cannot properly define * * JAVA_HOME when migrating from V5.1 to * * V7 on iSeries. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Webshere Application Server V5.1 case for locating and defining the JAVA_HOME was not handled when changes to the code were introduced for iSeries V7R1 JAVA_HOME restrictions.
Problem conclusion
Added code to test for V5.1 and properly set the JAVA_HOME variable. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM15531
Reported component name
WAS NETWRK DEPL
Reported component ID
5630A3601
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-05-28
Closed date
2010-06-08
Last modified date
2010-06-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
10 February 2022