Fixes are available
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
If customers are migrating from a WebSphere server that used to run V6.1 at some point but convertScriptCompatibility tool was never ran, there is no more option for this update during migration to V9.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V9.0 migration scripts * **************************************************************** * PROBLEM DESCRIPTION: Migration fails if the old cell * * being migrated has not been converted * * to the new security model. * **************************************************************** * RECOMMENDATION: * **************************************************************** A version 9.0 Deployment Manager cannot support federated nodes which are older that version 7.0 in a mixed cell environemnt. Therefore, version 9.0 migration assumes that the cell has been converted to the newer configuration model introduced in version 6.0.2. However, it appears that once the old cell had completed migration to a v7.0 environment the "convertScriptCompatibility" was never run - thus the version 7.0 cell was still running with a v6.0.1 configuration model. Therefore, we need to provide away for version 9.0 migration to handle the conversion of the old model to the new model.
Problem conclusion
Provide a system property that allows the Version 9.0 migration code to handle the conversion of the config model. In reality this conversion should take place prior to migrating to version 9.0 using the convertScriptCompatibility script. However, some have requested this be support during a migration. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.8. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI93488
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-09
Closed date
2018-05-30
Last modified date
2018-05-30
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
04 May 2022