New hardware for a RAC on AIX
From: Hubler, Daniel <daniel.hubler_at_aurora.org>
Date: Wed, 6 May 2015 22:11:36 +0000
Message-ID: <850425C04FB76547AC0ED12C5F7E0B804153354D_at_HEIMSEAT021.ahc.root.loc>
Looking for opinions, anecdotes and comments on the following. . . . .
Date: Wed, 6 May 2015 22:11:36 +0000
Message-ID: <850425C04FB76547AC0ED12C5F7E0B804153354D_at_HEIMSEAT021.ahc.root.loc>
Looking for opinions, anecdotes and comments on the following. . . . .
We have a 2-node RAC on IBM/AIX hardware. Management has decided it is time to retire this hardware.
We have been discussing strategies for moving the new hardware into place. There are now 2 opinions on how this could be/should be done:
- Follow the RAC administration guide adding a new node into the cluster, and then take an old node away. The cluster grows from 2 nodes, to 3 nodes, then back to 2 nodes.
- Move the new hardware into place using the following steps:
- generate a MKSYSB of the LPAR to be replaced
- shut down the LPAR to be replaced
- create an LPAR on the new hardware, using the MKSYSB from the old hardware
- present the LUNs that were on the old node, to the new node
- start up the LPAR on the new hardware; start up RAC
(and of course, the whole thing would have to be done twice; once for each node in the cluster)
Plan "b" is a bit more involved than I present above. It has been used successfully, many times, on LPARS that are running stand-alone databases; not RAC.
We are a bit leery about executing plan "b" against an LPAR running RAC, but we really cannot see why it will not work.
Any thoughts appreciated.
Daniel Hubler
Aurora Healthcare
IT Infrastructure
-- http://www.freelists.org/webpage/oracle-lReceived on Thu May 07 2015 - 00:11:36 CEST