PI89175: WASPREUPGRADE.SH WITH "-MACHINECHANGE TRUE" FAILS WITH ERROR MIGR0104E

Fixes are available

APAR status

Closed as program error.

Error description

Client is attempting to do a remove migration from WAS V7 to
WAS V8.5.5.
These are the steps that caused the problem:
1. He ran this command on the WAS V855 installation:
./createRemoteMigrJar.sh -targetDir /tmp/preupgrade -skipJava
2. He copied the jar file to /opt/IBM/WebSphere/migrate on his
WAS V7 machine and extracted it.
3. From /opt/IBM/WebSphere/migrate/bin he ran the command:
./WASPreUpgrade.sh /tmp/preupgrade
/opt/IBM/WebSphere/AppServer/ -machineChange true
4. If fails with error
 "MIGR0104E: You must specify the currently installed
Application Server directory name."
5. Running versionInfo.sh shows the information about WAS V7.
 --
The WASPreUpgrade.sh command thinks it is running from the WAS
V7 product and not WAS V885.
The problem was caused by this setting in the
/opt/IBM/WebSphere/migrate/properties/wasprofile.properties
file:
WS_PROFILE_REGISTRY=/opt/IBM/WebSphere/Profiles/properties/
profileRegistry.xml
Since this value is valid on the WAS V7 system it causes the
WAS V7 product to used instead on WAS V885.

Local fix

The client worked around the problem by commenting out
WS_PROFILE_REGISTRY=/opt/IBM/WebSphere/Profiles/properties/profi
leRegistry.xml
in /opt/IBM/WebSphere/migrate/properties/wasprofile.properties
file.

Keywords: migation migrate migrating waspreupgrade
waspostupgrade wl3mig

Problem summary

****************************************************************
* USERS AFFECTED:  All users of the IBM WebSphere Application  *
*                  Server Remote Migration Tool                *
****************************************************************
* PROBLEM DESCRIPTION: The remote WASPreUpgrade tool is        *
*                      calling the version of the tool.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When source and target installations are set up with similar
paths to the profile registry in the wasprofile.properties
file, the setupCmdLine script gets confused and incorrectly
sets may WAS variables incorrectly.  Thus is tries to run the
wrong version of the WASPreUpgrade command.

Problem conclusion

When gathering the necessary data/files for the remote
migration jar, simply set the location of the profile registry
value back to its default location in the
wasprofile.properties file.  The default prepends the location
with a ${was.install.root} variable.  This causes the
setupCmdLine to find the WASPreUpgrade command from the
correct location.

The fix for this APAR is currently targeted for inclusion in
fix pack 9.0.0.6 and 8.5.5.13.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Remove the WAS_PROFILE_REGISTRY variable from the
wasprofile.properties file in the remote migration directory.

Comments

APAR Information

APAR number
PI89175
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-10-20
Closed date
2017-12-14
Last modified date
2017-12-14

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R850 PSY
UP
R900 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI89175: WASPREUPGRADE.SH WITH "-MACHINECHANGE TRUE" FAILS WITH ERROR MIGR0104E

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?