From: Iain Barker (ibarker@aastra.com)
Date: Wed Oct 22 2003 - 13:29:23 EDT
Has anyone experienced problems upgrading from PK7 to PK8 on a 4.0f system
with TruCluster ?
I am seeing patch apply failures from PK8 due to blocking by PK7 standard
patches : NOT CSPs or -E-/-ES- patches but patches from the standard PK7
patchkit.
HP support are saying nobody else has complained of this problem. Yet today
I did a new install of 4.0f and TCR 1.6, with PK7 then installed on top.
Then I applied PK8 and saw the same dependency problem on three patches.
I am doing this one system as a dry-run for the same upgrade to roll out on
over 100 servers, this doesn't look good so far... I get the following
errors relating to NON-CSP PATCHES from the previous patchkit 7 blocking the
application of PK8.
-------------------------------------------------------------------------
Problem installing:
- TruCluster_V1.6 / ASE Availability Manager Patches:
Patch 00088.00 - Fixes a problem that causes asedirector to core
dump
requires the existence of the following un-installed/un-selected subset(s):
- TruCluster_V1.6 / Cluster Services Patches:
Patch 00099.00 - clu_ivp script enhancements
This patch will not be installed.
-------------------------------------------------------------------------
The reason patch 88 will not install is that it has a dependency on patch
99. But patch 99 won't install because patch 89 from pk7 is already
installed!!!
It looks to me like HP have the patch numbering wrong in PK8 compared to
PK7:
PK7 contains:
TCRPAT00008400160 Patch: LSM disk information not updated in ASE database
TCRPAT00008700160 Patch: Fixes a DLM problem
TCRPAT00008900160 Patch: Fix for Oracle process hang
PK8 contains:
TCRPAT00009400160 Patch: LSM disk information not updated in ASE database
TCRPAT00009700160 Patch: Processes may get referenced several times
TCRPAT00009900160 Patch: clu_ivp script enhancements
Although the descriptions are different in some cases, looking at the file
content these three patches appear to be identical between PK7 and PK8, but
the patch number differs by 10 between BL18 and BL22 versions.
i.e. pk7 and pk8 have different patch ID's for the same content, which
breaks the dependency checking. Later pk8 patches such as patch 88 can't
apply due to the error, and patch 88 is quite a critical patch for
TruCluster users.
Does anyone else see the same or similar problems?
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:39 EDT