PQ85230: UPDATEINSTALLER ALLOWS EARLIER DATED CUMULATIVE FIXES TO BE INSTALLED OVER TOP OF THE LATEST CUMULATIVE FIX. | |||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Scenario: A component has produced several cumulative fixes: A WAS_Workflow_01-15-2004_5.0.2_cumulative B WAS_Workflow_01-16-2004_5.0.2_cumulative C WAS_Workflow_01-17-2004_5.0.2_cumulative D WAS_Workflow_01-18-2004_5.0.2_cumulative E WAS_Workflow_02-15-2004_5.0.2_cumulative F WAS_Workflow_02-16-2004_5.0.2_cumulative G WAS_Workflow_02-17-2004_5.0.2_cumulative H WAS_Workflow_02-18-2004_5.0.2_cumulative If ONLY cumulative fix H is installed on a WAS 5.0.2 enterprise system, the update installer prevents cumulative fixes A-G from being installed. This indicates that the ifixDriver must have the correct specification. However if cumulative fix C is installed followed by cumulative fix H, it is then possible to install any of the other cumulative fixes D-G. Yet A and B will not install. Another example: install A then C then B - no warnings. B is installed. The installer is only looking at the info from the first cumulative installed for the comparisons, to install or not. To resolve : The date used for comparisons must be updated as each new cumulative is installed.Local fix If an earlier version was installed the user can install again the latest version or uninstall the old cumulative, install the latest.Problem summary **************************************************************** * USERS AFFECTED: Users installing multiple cumulative * * fixpacks on WebSphere Application Server * * 5.0 and 5.1 using the Update Installer. * **************************************************************** * PROBLEM DESCRIPTION: The cumulative fixpacks where not * * meeting their prerequisites checks * * correctly and causing the incorrect * * order of installs. * * * * For example, show the install of the * * following cumulative fixpacks to * * show the incorrect behaviour. * * * * 1. Install 2/18/2004 fix, then try * * install 1/15/2004 fix - this is * * prevented correctly. * * * * 2. Install 1/15/2004 fix, then * * install 2/18/2004 fix, then * * 1/16/2004 fix. This is not * * prevented but rather allowed to * * incorrectly proceed. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Update Installer was not updating the fixes correctly in the history and getting itself confused.Problem conclusion The Update Installer has been updated to correctly keep track of cumulative fixapacks and not allow incorrect order of installs.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
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > Enterprise Edition (EE)
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ85230
IBM Group: Software Group
Modified date: Mar 24, 2004
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.