PQ56441: MIGRATION TO WAS 4.0 GETS MIGR0121E & MIGR0124E IF IMPORT ADMIN DB DRIVER IF NO DATASOURCE REFERENCES THIS JDBC DRIVER. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description While using Migration tools to migrate from WebSphere 3.5.x to 4.0.1 or 4.0.2 user received the following errors in the log migration.log. MIGR0121E and MIGR0124E. Log file had entries: MIGR0219I: Starting to import JDBC Drivers. MIGR0218I: Starting to import Admin DB Driver, action update. com.ibm.websphere.migration.exceptions.WASUpgradeInvalidArgument Exception: MIGR0121E: Unable to read import XML document /opt/ibm/was/migration/backup/websphere_3x_backup.xml, exception MIGR0124E: Unable to import XML data file java.lang.NullPointerException.. This problem is caused by the fact that no data source is using the "Admin DB Driver". This is only true for the "Admin DB Driver". If another driver is added that is not used by a Data Source it will not cause problems. To remedy this remove the "Admin DB Driver" from the websphere_3x_backup.xml or from the 3.x repository before doing the WASPreUpgrade process.Local fix To remedy this remove the "Admin DB Driver" from the websphere_3x_backup.xml or from the 3.x repository before doing the WASPreUpgrade process.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * who migrate when no Data Source is * * configured on the Admin DB Driver * **************************************************************** * PROBLEM DESCRIPTION: A java.lang.NullPointerException is * * thrown when XMLConfig attempts to * * import the websphere_4x_restore.xml * * file created by migration. * **************************************************************** * RECOMMENDATION: * **************************************************************** When migrating from WebSphere 3.x to 4.0, a java.lang. NullPointer exception is thrown when XMLConfig attempts to import the websphere_4x_restore.xml file if no Data source is configured on the Admin DB Driver. The exception is thrown when the Admin DB Driver is being imported.Problem conclusion Code has been added that checks to see if any Data sources are configured on the Admin DB Driver. If there are no Data sources configued on the Admin DB Driver, the Admin DB Driver will not be migrated from WebSphere 3.x to 4.0.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ56441
IBM Group: Software Group
Modified date: Feb 8, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.