PK58098: MIGR0286E NOTFOUNDEXCEPTION ON RAR FILE - WASPOSTUPGRADE STEP INMIGRATION IF WAS_INSTALL_ROOT / USER_INSTALL_ROOT HAS SYMLINKS

 Fixes are available

6.1.0.17 WebSphere Application Server V6.1 Fix Pack 17 for i5/OS
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Linux
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Solaris
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for HP-UX
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Windows
6.1.0.17 WebSphere Application Server V6.1 Fix Pack 17 for AIX
6.1.0.19 WebSphere Application Server V6.1 Fix Pack 19 for AIX
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for HP-UX
6.1.0.19 WebSphere Application Server V6.1 Fix Pack 19 for i5/OS
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Linux
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Solaris
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Windows
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server



APAR status
Closed as program error.

Error description
This issue also present with APAR 
PK48599 and technote 1257063:
issue: 
http://www-1.ibm.com/support/docview.wss?uid=swg21257063
.
Please note that APAR 
PK48599 is *not PE*. Please review the
Responder text of this APAR and 
PK48599 for differences in these
two fixes.
.
During migrating to V6.0.2 or 6.1 of IBMᄅ WebSphereᄅ Application
Server for z/OS, in the WASPostUpgrade step of the migration,
the following exception was seen,

com.ibm.ws.migration.utility.UpgradeException:
com.ibm.wsspi.migration.document.exceptions.NotFoundException:
/Z1/was60t1/AppServerZ1/profiles/default/installedConnectors/ims
ico.rar/
.at
com.ibm.ws.migration.postupgrade.Restore.<init>(Restore.java:249
)
.at
com.ibm.ws.migration.postupgrade.WASPostUpgrade.restore(WASPostU
pgrade.java:231)
.at
com.ibm.ws.migration.postupgrade.WASPostUpgrade.main(WASPostUpgr
ade.java:114)
.
.
MIGR0286E: The migration failed to complete.

Service levels V6.1.0.3/ 6.0.2.15 shipped apars that addressed a
similar problem, however that was a defect and was not caused by
the presence of symlinks as was the case here. So this problem
is seen even after applying V6.1.0.3/ 6.0.2.15.
Local fix
Please also refer to technote 1257063 for a description and
workaround of this issue:

http://www-1.ibm.com/support/docview.wss?uid=swg21257063

Regenerate the migration jobs so that all paths are absolute and
there are no symlinks coded. Also, it must be ensured that the
variables WAS_INSTALL_ROOT and USER_INTALL_ROOT of the node to
be migrated point to the non-symlink path. In this case that was
/Z1/was60t1/AppServerZ1.

The variables WAS_INSTALL_ROOT and USER_INTALL_ROOT can be
changed through the administrative console. They also must be
changed in the setupCmdLine.sh script. This is for the node that
is being migrated. The HFS must be backed up before this change
in case there are problems changing the variables.

After the changes, the migration job was rerun and the problem
was resolved.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V6.1 for z/OS migrating from configurations  *
*                 where the WebSphere install path contains    *
*                 one or more symlinks and custom installed    *
*                 J2C connectors.                              *
****************************************************************
* PROBLEM DESCRIPTION: Customers would find that migration     *
*                      could not locate files to copy during   *
*                      the Pre and Post upgrade steps, which   *
*                      required the customer to manually       *
*                      copy those files.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This error was caused by a mismatch between the product install
path, the WebSphere variables for install locations, and the
paths provided in the migration jobs (3D, 3F, 3B) via the
configuration panels or the zMMT.
Problem conclusion
The migration algorithm for resolving file paths has been
hardened to more rigorously locate files that are along
symlinked paths, and provide the copy support if the path can
be determined to fit within one of the possible symlinked
paths described in the Problem Summary above.

APAR PK58098 is currently targeted for inclusion in Service
Level (Fix Pack) 6.1.0.17 of WebSphere Application Server V6.1
for z/OS.
Temporary fix Comments
APAR information
APAR number PK58098
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 610
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2007-12-12
Closed date 2008-04-07
Last modified date 2008-07-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSN    UP
R601 PSN    UP
R610 PSY UK36750    UP08/06/10 P F806

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK58098.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK58098
IBM Group: Software Group
Modified date: Jul 2, 2008