Fixes are available
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
Install WebSphere Application Server offering such as Base 8.5.0.1 or 8.5.5.0 with core.feature and 32-bit SDK feature. Try to modify SDK feature to 64-bit by imcl command. You would expect this silent modify to be blocked because the SDK feature is not allowed to be modified. However, in 8.5.0.1 or later version, the block bundle does not seem to be working, and lets the modify continue, until you get a failure: "CRIMA1020E ERROR: Failed to extract zip com.ibm.websphere.JDK6.32bit.jre_002_linux.ppc32_x 8.5.1.201210040426. File /test/root/installs/AppServer/java/./jre/lib/rt.jar already exists. " This is a regression issue, the blocking bundle worked well on 8.0.0.5 and 8.5.0.0. But not in 8.5.0.1.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Attempts to change SDK from 64-bit to * * 32-bit or from 32-bit to 64-bit with * * update, modify, or rollback causes * * installation of new SDK to fail * **************************************************************** * RECOMMENDATION: * **************************************************************** If you try to modify SDK for 32-bit to 64-bit or 64-bit to 32-bit, the SDK bundle will block the operation. However the sdk bundle shares the same dataKey="user.featuresRequired.1" with the feature validation bundle. And sometimes, the SDK bundle is not called. Another issue is the bundle does not validate SDK features when updating or rollback.
Problem conclusion
To prevent the problem we now: 1. Use a different dataKey for com.ibm.ws.sdk.feature.v85 bundle dataKey="user.sdk.featuresRequired". 2. Implement validation methods for update and rollback opertations. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.6, and 8.5.0.2. 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
PM76516
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-05
Closed date
2013-01-02
Last modified date
2013-03-01
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
02 November 2021