UPDATE: Confirming Patch Kit Installation

From: rob.leadbeater@lynx.co.uk
Date: Tue Aug 31 2004 - 06:00:18 EDT


Hi,

I've had a number of suggestions:

Iain Barker:
setld -i and check that all subsets are installed.
They are.

Martin Andersen:
Try reversing the patch installation / restore.
I'll leave this to a last resort as the box is in production for other things.

John Lanier:
Check /var/adm/patch/log/session.log and /cluster/admin/clu_upgrade
These don't show any thing notable. session.log is missing entries relating to moving the new kernel compared to our test system, as I'd expect, but nothing else stands out.

Any other suggestions ?

Cheers,

Rob

> -----Original Message-----
> From: tru64-unix-managers-owner@ornl.gov
> [mailto:tru64-unix-managers-owner@ornl.gov] On Behalf Of
> rob.leadbeater@lynx.co.uk
> Sent: 28 August 2004 16:27
> To: tru64-unix-managers@ornl.gov
> Subject: Confirming Patch Kit Installation
>
>
> Hi managers,
>
> During a non-rolling installation of Patch Kit 4 on a 2 node
> memory channel,
> 5.1B cluster, I inadvertently CTRL-C'd the window running dupatch.
>
> This happened towards the end of the installation, just as node 2 was
> rebooting (dupatch was running on node 1).
>
> I tried running dupatch again, to see what would happen,
> however this stated
> that all patches were installed. I was just going to reboot
> node 1, but
> noticed that the correct kernel had not been copied into
> place on node 1, so
> I manually copied it from /sys/NODE1/vmunix to
> /cluster/members/member1/boot_partition/vmunix and then rebooted.
>
> Everything appeared to be working OK, however we have
> subsequently tried to
> do an installation of Oracle 10g database on the cluster,
> which is behaving
> rather strangely compared to our test system.
>
> Is there any way to check that the patch kit install did complete
> successfully ?
>
> Regards,
>
> Rob
>
>
>
>
> This message is intended only for the use of the person(s)
> ("The intended
> Recipient(s)") to whom it is addressed. It may contain
> information which
> is privileged and confidential within the meaning of
> applicable law. If
> you are not the intended recipient, please contact the sender
> as soon as
> possible. The views expressed in this communication are not
> necessarily
> those held by LYNX Express Limited.
>
>



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:07 EDT