This procedure relies on the following prerequisites and assumptions.
You are using both Oracle Real Application Clusters and failover or scalable data services.
If you are using only Oracle Real Application Clusters, follow the instructions in SPARC: How to Replace a Host Adapter When Using Oracle Real Application Clusters Only. If you are using only failover and scalable data services, follow the instructions in How to Replace a Host Adapter When Using Failover and Scalable Data Services Only.
Except for the failed host adapter, your cluster is operational and all nodes are powered on.
If your nodes are configured for dynamic reconfiguration, see the Sun Cluster system administration documentation, and skip steps that instruct you to shut down the node.
Does your cluster use both failover or scalable data services and Oracle Real Application Clusters?
If no, follow the instructions in SPARC: How to Replace a Host Adapter When Using Oracle Real Application Clusters Only or How to Replace a Host Adapter When Using Failover and Scalable Data Services Only.
If yes, proceed to Step 2.
Determine the Oracle instance that is running on Node A.
# ps -ef | grep oracle |
Shut down the Oracle Real Application Clusters instance identified in Step 2.
For information about how to shut down and restart an Oracle instance in the RAC environment, refer to the Oracle 9iRAC Administration Guide.
Determine the resource groups and device groups that are running on Node A.
Record this information because you use it in Step 18 of this procedure to return resource groups and device groups to Node A.
# scstat |
Move all resource groups and device groups off Node A.
# scswitch -S -h nodename |
Determine if the storage device that is connected to the failed host adapter contains a quorum device.
# scstat -q |
If Node A contains a quorum device, add a new quorum device on a different storage device and remove the old quorum device.
For procedures about how to add and remove quorum devices, see the Sun Cluster system administration documentation.
Detach the VERITAS Volume Manager plexes on the storage array that is attached to the failed host adapter.
For more information, see your VERITAS Volume Manager documentation.
Record the details of plexes that are affected by the failed host adapter.
Record this information because you use it in Step 18 of this procedure to reattach plexes on the storage array. For more information about how to determine which plexes are affected, see your VERITAS Volume Manager documentation.
Is Node A enabled with the Solaris dynamic reconfiguration (DR) feature?
For more information, see your Sun Cluster system administration documentation.
Shut down Node A.
For the full procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
Power off Node A.
Replace the failed host adapter.
For the procedure about how to remove and add host adapters, see the documentation that shipped with your nodes.
Is Node A enabled with the Solaris DR feature?
For more information, see your Sun Cluster system administration documentation.
Power on Node A.
Boot Node A into cluster mode.
For more information about how to boot nodes, see your Sun Cluster system administration documentation.
If necessary, upgrade the host adapter firmware on Node A.
PatchPro is a patch-management tool that eases the selection and download of patches required for installation or maintenance of Sun Cluster software. PatchPro provides an Interactive Mode tool especially for Sun Cluster. The Interactive Tool makes the installation of patches easier. PatchPro's Expert Mode tool helps you to maintain your configuration with the latest set of patches. Expert Mode is especially useful for obtaining all of the latest patches, not just the high availability and security patches.
To access the PatchPro tool for Sun Cluster software, go to http://www.sun.com/PatchPro/, click Sun Cluster, then choose either Interactive Mode or Expert Mode. Follow the instructions in the PatchPro tool to describe your cluster configuration and download the patches.
For third-party firmware patches, see the SunSolveSM Online site at http://sunsolve.ebay.sun.com.
Reattach the VERITAS Volume Manager plexes on the storage array to their respective volumes.
For more information, see your VERITAS Volume Manager documentation.
(Optional) If necessary, return the resource groups and device groups you identified in Step 5 to Node A.
# scswitch -z -g resource-group -h nodename # scswitch -z -D device-group-name -h nodename |
For more information, see your Sun Cluster system administration documentation.
(Optional) Bring your Oracle Real Application Clusters instance online. This is the instance you identified in Step 2.
For information about how to shut down and restart an Oracle instance in the RAC environment, refer to the Oracle 9iRAC Administration Guide.
(Optional) If you relocated a quorum device in Step 7 and you want your configuration to use the same quorum structure after the host adapter replacement, relocate the quorum device function back to this storage array.
For procedures about how to add and remove quorum devices, see the Sun Cluster system administration documentation.
In the following example, a two-node cluster is running Oracle Real Application Clusters and VERITAS Volume Manager. In this situation, you begin the host adapter replacement by determining the Oracle instance name.
# ps -ef | grep oracle oracle 14716 14414 0 14:05:47 console 0:00 grep oracle oracle 14438 1 0 13:05:44 ? 0:02 ora_lmon_tpcc1 . . . oracle 14434 1 0 13:05:43 ? 0:00 ora_pmon_tpcc1 oracle 14458 1 0 13:05:50 ? 0:00 ora_d000_tpcc1 |
This output identifies the Oracle Real Application Clusters instance as tpcc1.
Shutting down the Oracle Real Application Clusters instance on Node A involves several steps, as shown in the following example.
# su - oracle Sun Microsystems Inc. SunOS 5.9 Generic May 2002 $ ksh $ ORACLE_SID=tpcc1 $ ORACLE_HOME=/export/home/oracle/OraHome1 $ export ORACLE_SID ORACLE_HOME $ sqlplus " /as sysdba " SQL*Plus: Release 9.2.0.4.0 - Production on Mon Jan 5 14:12:28 2004 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options JServer Release 9.2.0.4.0 - Production SQL> shutdown immediate ; Database closed. Database dismounted. ORACLE instance shut down. SQL> exit Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options JServer Release 9.2.0.4.0 - Production $ lsnrctl LSNRCTL for Solaris: Version 9.2.0.4.0 - Production on 05-JAN-2004 14:15:09 Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved. Welcome to LSNRCTL, type "help" for information. LSNRCTL> stop Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) The command completed successfully LSNRCTL> |
After you have stopped the Oracle Real Application Clusters instance, check for a quorum device and, if necessary, reconfigure the quorum device.
When you are certain that the node with the failed adapter does not contain a quorum device, proceed to determine the affected plexes.
Record this information for use in reestablishing the original storage configuration. In the following example, c2 is the controller with the failed host adapter.
# vxprint -ht -g tpcc | grep c2 dm tpcc01 c2t0d0s2 sliced 4063 8374320 - dm tpcc02 c2t1d0s2 sliced 4063 8374320 - dm tpcc03 c2t2d0s2 sliced 4063 8374320 - dm tpcc04 c2t3d0s2 sliced 4063 8374320 - dm tpcc09 c2t8d0s2 sliced 4063 8374320 - dm tpcc10 c2t9d0s2 sliced 4063 8374320 - sd tpcc02-01 control_001-01 tpcc02 0 41040 0 c2t1d0 ENA . . . sd tpcc03-06 temp_0_0-02 tpcc03 2967840 276480 0 c2t2d0 ENA sd tpcc03-04 ware_0_0-02 tpcc03 2751840 95040 0 c2t2d0 ENA |
From this output, you can easily determine which plexes and subdisks are affected by the failed adapter. These are the plexes you detach from the storage array.
/usr/sbin/vxplex -g tpcc det control_001-02 /usr/sbin/vxplex -g tpcc det temp_0_0-02 |
After the plexes are detached, you can safely shut down the node, if necessary.
Proceed with replacing the failed host adapter, following instructions that accompanied that device.
After you replace the failed host adapter, and Node A is in cluster mode, reattach the plexes and replace any quorum device to reestablish your original cluster configuration.