PQ46685: MIGRATION ASSISTANT GIVES ERROR "IMPORT: CAN'T FIND LIBJVM.A"


APAR

APAR status
Closed as fixed if next.

Error description
The WAS migration assistant is trying to export classic threads
for whatever classes the customer uses and cannot find them in
the JRE that comes witht the WAS 3.5 install.  This points to a
defect in the migration script.
Local fix
Problem summary
The WAS migration assistant is trying to export classic threads
for whatever classes the customer uses and cannot find them in
the JRE that comes witht the WAS 3.5 install.  This points to a
defect in the migration script.
This will need to be addressed in the next full product
refresh.
Problem conclusion
Temporary fix
Manually work through migration steps:
 These main steps comprise migration:Manually work through migration steps:
Back up and configure the current administrative server Start the current administrative server. Export the XML configuration to a file. Update the XML configuration file. Backup configuration files. Uninstall WebSphere Application Server Version 3.0.2.x Stop all parts of the current product. Uninstall the current product. Drop the administrative database used for WAS 3.0.2.x Back up the database. You can use the database management syste Drop the database. Install WebSphere Application Server Version 3.5 Restore the old WebSphere Application Server configuration into Restore configuration files. Start the new administrative server. Import the XML configuration file.
These main steps comprise migration:Back up and configure the current administrative serverStart the current administrative server.Export the XML configuration to a file.Update the XML configuration file.Backup configuration files.Uninstall WebSphere Application Server Version 3.0.2.xStop all parts of the current product.Uninstall the current product.Drop the administrative database used for WAS 3.0.2.xBack up the database. You can use the database management systeDrop the database.Install WebSphere Application Server Version 3.5Restore the old WebSphere Application Server configuration intoRestore configuration files.Start the new administrative server.Import the XML configuration file.
Comments
APAR information
APAR numberPQ46685
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED FIN
PENoPE
HIPERNoHIPER
Submitted date2001-03-05
Closed date2001-03-19
Last modified date2001-03-19

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
INSTALL
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information

Applicable component levels
R350 PSNUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ46685
IBM Group: Software Group
Modified date: 2001-03-19