PK44889: MIGR0445W MESSAGE DURING MIGRATION FROM V 5.1 DUE TO BAD IMPLEMENTATIONCLASSNAME IN RESOURCES.XML

 Fixes are available

6.1.0.15 WebSphere Application Server V6.1 Fix Pack 15 for i5/OS
6.1.0.13 WebSphere Application Server V6.1 Fix Pack 13 for AIX
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for AIX platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for HP-UX platforms
6.1.0.15 WebSphere Application Server V6.1 Fix Pack 15 for AIX
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for HP-UX
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for Windows
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for OS/400 platform
6.1.0.13: WebSphere Application Server V6.1 Fix Pack 13 for Windows
6.1.0.17 WebSphere Application Server V6.1 Fix Pack 17 for i5/OS
6.1.0.13: WebSphere Application Server V6.1 Fix Pack 13 for i5/OS
6.1.0.13: WebSphere Application Server V6.1 Fix Pack 13 for HP-UX
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Solaris
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Windows platforms
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Linux
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for AIX platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for HP-UX platforms
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.13: WebSphere Application Server V6.1 Fix Pack 13 for Solaris
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for Linux
6.1.0.15: WebSphere Application Server V6.1 Fix Pack 15 for Solaris
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for AIX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for HP-UX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Linux platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Solaris
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Windows platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Linux platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Linux platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Solaris
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Windows platforms
6.1.0.13: WebSphere Application Server V6.1 Fix Pack 13 for Linux
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
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for AIX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for HP-UX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for OS/400 platform
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Linux platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Solaris
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Windows platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server



APAR status
Closed as program error.

Error description
The following error may occur when migration from WAS 5.1 to
WAS 6.x:

MIGR0445W: The JDBC provider, DB2 Universal JDBC Driver
Provider, is no longer a valid JDBC provider. You will not be
able to create any new data sources for this provider. To create
a new data source you must create a new JDBC provider.

This message can be caused by bad implementationClassName
specified for either of these 2 JDBC providers:
DB2 for zOS Local JDBC Provider (RRS)
DB2 Universal JDBC Driver Provider

The bad value can be seen in the admin console as well as
resources.xml file:
implementationClassName="com.ibm.db2.jcc.DB2ConnectionPoolDataSo
urce for NonXa DB2 Universal Provider"

The correct value is:
implementationClassName="com.ibm.db2.jcc.DB2ConnectionPoolDataSo
urce"

Migration checks this setting to determine the datasource type.
Because of bad definition, it does not recognize it as a valid
JDBC provider.  Neither runtime for V5.1 or 6.x is affected by
this problem.  The JDBC Providers continue to run.  However,
part of the migration of the defined JDBC provider is to add a
new tag to the definition of the provider: providerType.  Since
migration does not recognize it as a valid jdbc provider, this
tag is not added.

This apar will fix migration to recognize the provider as valid
and will therefore add the appropriate providerType tag.
Local fix
After migration, the extra characters from implementationClassNa
me are removed.  However, providerType tag is not added.
Certain wsadmin function might not work without this tag.
Follow one of the following options to update your configuration
with providerType tag:

<< Link to the technote with the steps to be added soon >>
Problem summary
****************************************************************
* USERS AFFECTED: Users migrating from WebSphere Application   *
*                 Server V5.1.0 for z/OS to WebSphere          *
*                 Application Server V6.0.1 for z/OS           *
****************************************************************
* PROBLEM DESCRIPTION: The following warning may appear when   *
*                      migrating from WebSphere Application    *
*                      Server V5.1.0 to WebSphere Application  *
*                      Server V6.0.1:                          *
*                                                              *
*                      MIGR0445W: The JDBC provider, DB2       *
*                      Universal JDBC Driver Provider, is no   *
*                      longer a valid JDBC provider. You       *
*                      will not be able to create any new      *
*                      data sources for this provider. To      *
*                      create a new data source you must       *
*                      create a new JDBC provider.             *
*                                                              *
*                      The bad value can be seen in the admin  *
*                      console as well as resources.xml file:  *
*                      implementationClassName=                *
*                      "com.ibm.db2.jcc.DB2ConnectionPoolData  *
*                      Source for NonXa DB2 Universal          *
*                      Provider"                               *
*                                                              *
*                      The correct value is:                   *
*                      implementationClassName=                *
*                      "com.ibm.db2.jcc.DB2ConnectionPoolData  *
*                      Source"                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Migration checks this setting to determine the datasource type.
Because of a bad definition, it does not recognize it as a
valid JDBC provider.  Neither the V5.1.0 nor 6.1.0 runtime is
affected by this problem.  The JDBC Providers continue to run.
However, part of the migration process of the defined JDBC
provider is to add a new tag to the definition of the provider:
'providerType'.  Since migration does not recognize it as a
valid jdbc provider, this tag is not added.
Problem conclusion
This APAR corrects migration to recognize the provider as valid
so that it will now add the appropriate 'providerType' tag.

APAR PK44889 is currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.25 of WebSphere Application Server
V6.0.1 for z/OS.
Temporary fix Comments
APAR information
APAR number PK44889
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 601
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2007-05-09
Closed date 2007-10-19
Last modified date 2008-02-02

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

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 PSY UK32785    UP08/01/23 P F801
R610 PSN    UP

  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: swg1PK44889.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 601
Software edition:
Reference #: PK44889
IBM Group: Software Group
Modified date: Feb 2, 2008