Sun Cluster Installation Guide With Oracle HA

SUN Cluster 3.
1Installation Guide
Table of Contents
1. 1.1. 1.2. 1.3. 1.4. 1.5. 2. 2.1. 3. 4. 4.1. 4.2. 4.3. 4.4. 5. 6. 7. 8. 8.1. 9. 10. 11. 12. INSTALLATION OF OS AND PATCHES.......................................................................... 2 INSTALL SOLARIS 9 ON BOTH V440.................................................................................... 2 APPLYING STANDARD PATCH FROM EIS-CD 1 ................................................................... 2 APPLY RECOMMENDED PATCHES FROM EIS-CD................................................................. 2 APPLYING SUN CLUSTER PATCHES ................................................................................... 2 INSTALLATION OF SAN FOUNDATION KIT WILL DETECT THE HBA CARDS ON SERVERS .......... 2 CONFIGURING STORAGE 3510 ...................................................................................... 3 CREATION OF LOGICAL DRIVE ........................................................................................... 5 CREATING AND MOUNTING OF VOLUMES ON SERVER ............................................ 9 CREATING MIRROR ....................................................................................................... 10 CREATING MIRROR FOR /ROOT ........................................................................................ 10 CREATING MIRROR FOR /SWAP ........................................................................................ 10 CREATING MIRROR FOR /ORACLE ..................................................................................... 11 CREATING MIRROR FOR /GLOBALDEVICES ........................................................................ 11 CONFIGURING IPMP FOR BOTH THE SERVERS FOR FAILOVER............................ 12 INSTALL ORACLE ON BOTH THE NODES WITH THE SAME CONFIG ..................... 14 INSTALL SUN CLUSTER 3.1 ON BOTH THE NODES .................................................. 14 CREATING METASET DEVICE (DEVICE GROUP) ....................................................... 30 CREATED PARTITIONS AND METADEVICES ........................................................................ 31 ADDING QUORUM DISK ................................................................................................ 31 INSTALLATION REGISTRATION OF ORACLE HA AGENT......................................... 32 ENABLE HASTORAGE+ FOR ORACLE INSTANCE .................................................... 46 CLUSTER COMMAND FOR FAILOVER TESTING........................................................ 46
12.1. STARTING THE MACHINE .................................................................................................. 46 12.2. SHUTTING DOWN THE MACHINE ....................................................................................... 46 12.3. SHUTTING DOWN SINGLE SYSTEM IN CLUSTER................................................................. 47 12.4. SWITCHING THE RESOURCES FROM PRIMARY NODE (TOM-DB1) TO SECONDARY NODE (TOM-DB2).................................................................................................................................. 47 12.5. STOPPING ORACLE RESOURCES WITHOUT SHUTTING DOWN THE CLUSTER SERVICES ......... 47 12.6. STARTING ORACLE RESOURCES IN THE CLUSTER SERVICES .............................................. 47
Platform Integration
Page 1
Wipro Confidential
SUN Cluster 3.1Installation Guide
1. Installation of OS and Patches
1.1. Install Solaris 9 on both v440 (/root - 15 GB, Swap 8GB, Oracle-10 GB) Hostname TOM-db1 Hostname - TOM-db2 1.2. Applying Standard patch from EIS-CD 1 # cd /cdrom/cdrom0/sun/install # sh setup-standard.sh After installation of standard patches Logout/Login again Shell promt will be displayed with server name #root@TOM-db1 1.3. Apply recommended patches from EIS-CD # cd /cdrom/cdrom0/sun/patch/9 # unpack-patches ( it will unpack all the patches in tmp/9 folder ) # cd /tmp/9 #. /install_all_patches
1.4. Applying Sun Cluster Patches # cd /SUN/PATCH/SUNCLUST/3.X/3.1/9 # unpack-patches # cd /tmp/9 #. /install patches 1.5. Installation of SAN foundation kit will detect the HBA cards on servers Applying patches for SAN from EIS-CD SAN directory (111847) # CD /SUN/patch/SAN/9 # Unpack-patches # cd /tmp/9 # ./install_patches After Installation of patches (reboot the server ) # init 6
Page 2
Wipro Confidential
2. Configuring Storage 3510

The RS-232 COM port on controller module is used to configure and monitor the RAID array. It can be connected to a VT100 terminal or terminal emulation program, to a terminal server, or to the serial port of a Solaris host. Use a null modem serial cable to connect the COM port of the RAID array to the serial port on a host workstation. A null modem serial cable is included in the storage package contents. Set the serial port parameters on the workstation as follows: _ 38400 baud _ 8 bit _ 1 stop bit _ No parity Once the Storage is powered on the initial screen will be like as shown below
Page 3
Wipro Confidential
Select on Terminal VT100 mode. The 3510-1FC Main Menu appears. Select View and edit Configuration Parameters
Go to Communication Parameters Internet Protocol -> Set IP address. Type the desired IP address, netmask and default gateway.
Page 4
Wipro Confidential
The IP address for the storage is 192.9.200.100 2.1. Creation of Logical Drive 1. From the Main Menu and select view and edit Logical drives. Select the first available unassigned logical drive (LG) and press Return to create Logical drive 2. When prompted to Create Logical Drive? select Yes and press Return to proceed. A pull-down list of supported RAID levels is displayed. Select a RAID level for this logical drive. (In SBI RAID 5 is configured)
Page 5
Wipro Confidential
3. Select drive(s) from the list of available physical drives and press Return. The drives can be tagged for inclusion by highlighting the drive and then pressing Return. An asterisk mark (*) is displayed on the selected physical drive(s). To deselect a drive, press Return again on the selected drive. The asterisk disappears (There are total 18 disks in 3510 storage at SBI. 2 logical drives are created using 9 disks in each logical drive under RAID5. The logical drive P1 appears as fabric_0 and logical drive P2 appears as fabric_1 in the OS). 4. After all Physical drives are selected. Press Esc. Maximum drive capacity window appears with the values. Accept the default once by pressing Esc.
5. Now the Logical drive P1 is created. Repeat the same Steps (1 to 4) for creating additional logical drive P2.
Page 6
Wipro Confidential
6. After logical drives are created, Map the logical drives to Hosts. (In SBI, both logical drives P1 and P2 are mapped to both 480R servers since it is cluster configuration). 7. Both logical drives are mapped to channel 0 ID 40 and Channel 1 ID 41 as shown in the screen below.
Page 7
Wipro Confidential
8. Select View and Edit Configuration Parameters Drive-Side SCSI Parameters to enable the Periodic Auto-Detect Failure Drive Swap Check Time. This feature will enable the auto generation/re-build feature on 3510 whenever the new/replacement disk is inserted in 3510.
Page 8
Wipro Confidential
3. Creating and mounting of Volumes on server

# Create slice no.6 as globaldevices on both the nodes (Size 512MB) # Create Slice no.7 for metadabase on both the nodes (Size 256MB) # Create slice on storage and mount globally on both the server for e.g data1,data2 # newfs -f /dev/rdsk/c3t44d0s0 # newfs f /dev/rdsk/c3t40/d0s6 # mkdir /data1 # mkdir /data2 Mount the filesystem globally # mount -g /dev/dsk/c3t44/d0s0 /data1 # mount g /dev/dsk/c3t40/d0s7 /data2
Page 9
Wipro Confidential
4. Creating Mirror
# prtvtoc /dev/rdsk/c1t0d0s7 |fmthard -s - /dev/rdsk/c1t10d0s7 # metadb a f c5 c1t0d0s7 # metadb a c5 c1t1d0s7 4.1. Creating mirror for /root # metainit -f d10 1 1 c1t0d0s0 # metainit d11 1 1 c1t1dos0 Use the metainit -m command to create a one-way mirror with submirror1 # metainit d0 m d10 metaroot command edits the /etc/vfstab and /etc/system # metaroot d0 # reboot the server # metattach d0 d11 4.2. Creating mirror for /swap # metainit f d20 1 1 c1t0d0s1 # metainit d21 1 1 c1t1d0s1 # metainit d2 m d21 # metattach d2 d22
Page 10
Wipro Confidential
4.3. Creating mirror for /oracle # metainit f d30 1 1 c1t0d0s3 # metainit d31 1 1 c1t1d0s3 # metainit d3 m d30 # metattach d3 d31 4.4. Creating mirror for /Globaldevices # metainit d60 1 1 c1t0d0s6 # metainit d61 1 1 c1t1d0s6 # metainit d6 m d60 # metattach d6 d61 # metastat t | grep % to check the status of mirroring
Page 11
Wipro Confidential
5. Configuring IPMP for both the servers for failover

Make entry in /etc/hostname.ce0 & /etc/hostname.ce1 on both the server Node 1 # /etc/hostname.ce0 TOM-db1 netmask + broadcast + group IPMP up \ addif test-ce0 netmask + broadcast + deprecated -failover up # /etc/hostname.ce1 test-ce1 netmask + broadcast + group IPMP deprecated -failover standby up # /etc/hosts 127.0.0.1 localhost 192.168.1.3 TOM-db1 loghost 192.168.1.7 TOM-db2 192.168.1.4 test-ce0 192.168.1.9 test-ce1 192.168.1.5 TOM-db ( logical hostname ) Node 2 # /etc/hostname.ce0 TOM-db2 netmask + broadcast + group IPMP1 up \ addif test-ce0 netmask + broadcast + deprecated -failover up # /etc/hostname.ce1 test-ce1 netmask + broadcast + group IPMP1 deprecated -failover standby up # /etc/hosts 127.0.0.1 localhost 192.168.1.7 TOM-db2 loghost 192.168.1.3 TOM-db1 192.168.1.5 TOM-db (Logical Hostname ) 192.168.1.8 test-ce0 192.168.1.20 test-ce1 192.168.1.21
# init 6
Page 12
Wipro Confidential
# ifconfig -a lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255 groupname IPMP ether 0:3:ba:9d:bd:21 ce0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NO FAILOVER> mtu 1500 index 2 inet 192.168.1.4 netmask ffffff00 broadcast 192.168.1.255 ce0:2: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 2 inet 192.168.1.5 netmask ffffff00 broadcast 192.168.1.255 ce1: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,N OFAILOVER,STANDBY,INACTIVE> mtu 1500 index 3 inet 192.168.1.9 netmask ffffff00 broadcast 192.168.1.255 groupname IPMP ether 0:3:ba:b1:20:ec lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1 inet6 ::1/128 ce3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 4 inet 172.16.0.129 netmask ffffff80 broadcast 172.16.0.255 ether 0:3:ba:b1:20:ee ce5: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 5 inet 172.16.1.1 netmask ffffff80 broadcast 172.16.1.127 ether 0:3:ba:9d:bd:22 clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVAT E,IPv4> mtu 1500 index 6 inet 172.16.193.1 netmask ffffff00 broadcast 172.16.193.255 ether 0:0:0:0:0:1
Page 13
Wipro Confidential
6. Install Oracle on both the nodes with the same config 7. Install Sun Cluster 3.1 on both the nodes
# cd /cdrom/cdrom0 # ls Copyright License.txt # cd Sun* # ls Sol_8 Sol_9 # cd Sol_9 # cd Tools # scinstall *** Main Menu *** Please select from one of the following (*) options: * 1) Install a cluster or cluster node 2) Configure a cluster to be JumpStarted from this install server 3) Add support for new data services to this cluster node * 4) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: 1 *** Install Menu *** Please select from any one of the following options: 1) Install all nodes of a new cluster 2) Install just this machine as the first node of a new cluster 3) Add this machine as a node in an existing cluster ?) Help with menu options q) Return to the Main Menu Option: 2 *** Installing just the First Node of a New Cluster *** This option is used to establish a new cluster using this machine as the first node in that cluster.
Platform Integration Page 14 Wipro Confidential
README
SunCluster_3.1 index.html
Once the cluster framework software is installed, you will be asked for the name of the cluster. Then, you will have the opportunity to run sccheck(1M) to test this machine for basic Sun Cluster pre-configuration requirements. After sccheck(1M) passes, you will be asked for the names of the other nodes which will initially be joining that cluster. In addition, you will be asked to provide certain cluster transport configuration information. Press Control-d at any time to return to the Main Menu. Do you want to continue (yes/no) [yes]? yes >>> Software Package Installation <<< Installation of the Sun Cluster framework software packages will take a few minutes to complete. Is it okay to continue (yes/no) [yes]? yes ** Installing SunCluster 3.1 framework ** SUNWscr.....done SUNWscu.....done SUNWscsck...done SUNWscnm....done SUNWscdev...done SUNWscgds...done SUNWscman...done SUNWscsal...done SUNWscsam...done SUNWscvm....done SUNWmdm.....done SUNWscva....done SUNWscvr....done SUNWscvw....done SUNWscrsm...done SUNWfsc.....done SUNWfscvw...done SUNWjsc.....done SUNWjscman..done SUNWjscvw...done SUNWksc.....done SUNWkscvw...done SUNWcsc.....done SUNWcscvw...done SUNWhsc.....done SUNWhscvw...done SUNWexplo...done
Page 15
Wipro Confidential
Hit ENTER to continue: >>> Software Patch Installation <<< If there are any Solaris or Sun Cluster patches that need to be added as part of this Sun Cluster installation, scinstall can add them for you. All patches that need to be added must first be downloaded into a common patch directory. Patches can be downloaded into the patch directory either as individual patches or as patches grouped together into one or more tar, jar, or zip files. If a patch list file is provided in the patch directory, only those patches listed in the patch list file are installed. Otherwise, all patches found in the directory will be installed. Refer to the patchadd(1M) man page for more information regarding patch list files. Do you want scinstall to install patches for you (yes/no) [yes]? no >>> Cluster Name <<< Each cluster has a name assigned to it. The name can be made up of any characters other than whitespace. Each cluster name should be unique within the namespace of your enterprise. What is the name of the cluster you want to establish? TOMLClust. >>> Check <<< This step allows you to run sccheck(1M) to verify that certain basic hardware and software preconfiguration requirements have been met. If sccheck(1M) detects potential problems with configuring this machine as a cluster node, a report of failed checks is prepared and available for display on the screen. Data gathering and report generation can take several minutes, depending on system configuration. Do you want to run sccheck (yes/no) [yes]? Running sccheck ... sccheck: Requesting explorer data and node report from TOM-db1. sccheck: TOM-db1: Explorer finished. sccheck: TOM-db1: Starting single-node checks. sccheck: TOM-db1: Single-node checks finished. Press Enter to continue:
Page 16
Wipro Confidential
>>> Cluster Nodes <<< This Sun Cluster release supports a total of up to 16 nodes. Please list the names of the other nodes planned for the initial cluster configuration. List one node name per line. When finished, type Control-D: Node name: TOM-db2 Node name (Control-D to finish): ^D This is the complete list of nodes: TOM-db1 TOM-db2 Is it correct (yes/no) [yes]? yes >>> Authenticating Requests to Add Nodes <<< Once the first node establishes itself as a single node cluster, other nodes attempting to add themselves to the cluster configuration must be found on the list of nodes you just provided. You can modify this list using scconf(1M) or other tools once the cluster has been established. By default, nodes are not securely authenticated as they attempt to add themselves to the cluster configuration. This is generally considered adequate, since nodes which are not physically connected to the private cluster interconnect will never be able to actually join the cluster. However, DES authentication is available. If DES authentication is selected, you must configure all necessary encryption keys before any node will be allowed to join the cluster (see keyserv(1M), publickey(4)). Do you need to use DES authentication (yes/no) [no]? no >>> Network Address for the Cluster Transport <<< The private cluster transport uses a default network address of 172.16.0.0. But, if this network address is already in use elsewhere within your enterprise, you may need to select another address from the range of recommended private addresses (see RFC 1597 for details). If you do select another network address, bear in mind that the Sun Cluster software requires that the rightmost two octets always be zero. The default netmask is 255.255.0.0. You can select another netmask, as long as it minimally masks all bits given in the network address. Is it okay to accept the default network address (yes/no) [yes]? yes
Page 17
Wipro Confidential
Is it okay to accept the default netmask (yes/no) [yes]? yes >>> Point-to-Point Cables <<< The two nodes of a two-node cluster may use a directly connected interconnect. That is, no cluster transport junctions are configured. However, when there are greater than two nodes, this interactive form of scinstall assumes that there will be exactly two cluster transport junctions. Does this two-node cluster use transport junctions (yes/no) [yes]? No >>> Cluster Transport Adapters and Cables <<< You must configure at least two cluster transport adapters for each node in the cluster. These are the adapters which attach to the private cluster interconnect. Select the first cluster transport adapter: 1) ce1 2) ce2 3) ce3 4) ce4 5) ce5 6) other Option: 3 Adapter "ce3" is an Ethernet adapter. Searching for any unexpected network traffic on "ce3" ... done Verification completed. No traffic was detected over a 10 second sample period. The "dlpi" transport type will be set for this cluster. Select the second cluster transport adapter: 1) ce1 2) ce2 3) ce3 4) ce4 5) ce5 6) other Option: 5
Page 18
Wipro Confidential
Adapter "ce5" is an Ethernet adapter. Searching for any unexpected network traffic on "ce5" ... done Verification completed. No traffic was detected over a 10 second sample period. >>> Global Devices File System <<< Each node in the cluster must have a local file system mounted on /global/.devices/node@<nodeID> before it can successfully participate as a cluster member. Since the "nodeID" is not assigned until scinstall is run, scinstall will set this up for you. You must supply the name of either an already-mounted file system or raw disk partition which scinstall can use to create the global devices file system. This file system or partition should be at least 512 MB in size. If an already-mounted file system is used, the file system must be empty. If a raw disk partition is used, a new file system will be created for you. The default is to use /globaldevices. Is it okay to use this default (yes/no) [yes]? n Do you want to use an already existing file system (yes/no) [yes]?y What is the name of the file system? /globaldevices1 >>> Automatic Reboot <<< Once scinstall has successfully installed and initialized the Sun Cluster software for this machine, it will be necessary to reboot. After the reboot, this machine will be established as the first node in the new cluster. Do you want scinstall to reboot for you (yes/no) [yes]? no You will need to manually reboot this node in "cluster mode" after scinstall successfully completes. Press Enter to continue: >>> Confirmation <<< Your responses indicate the following options to scinstall:
scinstall -ik \ -C TOMLClust \

-F \ -G /globaldevices1 \ -T node=TOM-db1,node=TOM-db2,authtype=sys \ -A trtype=dlpi,name=ce2 -A trtype=dlpi,name=ce5 \ -B type=direct \ Are these the options you want to use (yes/no) [yes]? yes Do you want to continue with the install (yes/no) [yes]? yes Checking device to use for global devices file system ... done Checking device to use for global devices file system ... done Initializing cluster name to "TOMLClust" ... done Initializing authentication options ... done Initializing configuration for adapter "ce2" ... done Initializing configuration for adapter "ce5" ... done Setting the node ID for "TOM-db1" ... done (id=1) Setting the major number for the "did" driver ... done "did" driver major number set to 300 Checking for global devices global file system ... done Updating vfstab ... done Verifying that NTP is configured ... done Installing a default NTP configuration ... done Please complete the NTP configuration after scinstall has finished. Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done Adding the "cluster" switch to "hosts" in nsswitch.conf ... done Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done Verifying that power management is NOT configured ... done Unconfiguring power management ... done /etc/power.conf has been renamed to /etc/power.conf.041205145003 Power management is incompatible with the HA goals of the cluster. Please do not attempt to re-configure power management. Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done Ensure network routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter. Having a cluster node act as a router is not supported by Sun Cluster. Please do not re-enable network routing. Press Enter to continue:
Page 21
Wipro Confidential
*** Install Menu *** Please select from any one of the following options: 1) Install all nodes of a new cluster 2) Install just this machine as the first node of a new cluster 3) Add this machine as a node in an existing cluster ?) Help with menu options q) Return to the Main Menu Option: q *** Main Menu *** Please select from one of the following (*) options: 1) Install a cluster or cluster node 2) Configure a cluster to be JumpStarted from this install server * 3) Add support for new data services to this cluster node * 4) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: q Log file - /var/cluster/logs/install/scinstall.log.1027
Page 22
Wipro Confidential
On TOM-db2 After the TOM-db1 is started normally in cluster mode, Start the installation of Cluster on TOMdb2 as follows: #scinstall *** Main Menu *** Please select from one of the following (*) options: * 1) Install a cluster or cluster node 2) Configure a cluster to be JumpStarted from this install server 3) Add support for new data services to this cluster node * 4) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: 1 *** Install Menu *** Please select from any one of the following options: 1) Install all nodes of a new cluster 2) Install just this machine as the first node of a new cluster 3) Add this machine as a node in an existing cluster ?) Help with menu options q) Return to the Main Menu Option: 3 *** Adding a Node to an Existing Cluster *** This option is used to add this machine as a node in an already established cluster. If this is an initial cluster install, there may only be a single node which has established itself in the new cluster. Once the cluster framework software is installed, you will be asked to provide both the name of the cluster and the name of one of the nodes already in the cluster. Then, sccheck(1M) is run to test this machine for basic Sun Cluster pre-configuration requirements. After sccheck(1M) passes, you may be asked to provide certain cluster transport configuration information.
Press Control-d at any time to return to the Main Menu. Do you want to continue (yes/no) [yes]? >>> Software Patch Installation <<< If there are any Solaris or Sun Cluster patches that need to be added as part of this Sun Cluster installation, scinstall can add them for you. All patches that need to be added must first be downloaded into a common patch directory. Patches can be downloaded into the patch directory either as individual patches or as patches grouped together into one or more tar, jar, or zip files. If a patch list file is provided in the patch directory, only those patches listed in the patch list file are installed. Otherwise, all patches found in the directory will be installed. Refer to the patchadd(1M) man page for more information regarding patch list files. Do you want scinstall to install patches for you (yes/no) [yes]? no >>> Sponsoring Node <<< For any machine to join a cluster, it must identify a node in that cluster willing to "sponsor" its membership in the cluster. When configuring a new cluster, this "sponsor" node is typically the first node used to build the new cluster. However, if the cluster is already established, the "sponsoring" node can be any node in that cluster. Already established clusters can keep a list of hosts which are able to configure themselves as new cluster members. This machine should be in the join list of any cluster which it tries to join. If the list does not include this machine, you may need to add it using scconf(1M) or other tools. And, if the target cluster uses DES to authenticate new machines attempting to configure themselves as new cluster members, the necessary encryption keys must be configured before any attempt to join. What is the name of the sponsoring node [TOM-db1]? >>> Cluster Name <<< Each cluster has a name assigned to it. When adding a node to the cluster, you must identify the name of the cluster you are attempting to join. A sanity check is performed to verify that the "sponsoring" node is a member of that cluster. What is the name of the cluster you want to join [TOMLClust]? TOMLClust Attempting to contact "TOM-db1" ... done Cluster name "TOMLClust" is correct. Press Enter to continue:
>>> Check <<< This step allows you to run sccheck(1M) to verify that certain basic hardware and software preconfiguration requirements have been met. If sccheck(1M) detects potential problems with configuring this machine as a cluster node, a report of failed checks is prepared and available for display on the screen. Data gathering and report generation can take several minutes, depending on system configuration. Do you want to run sccheck (yes/no) [yes]? Running sccheck ... sccheck: Requesting explorer data and node report from . TOM-db2 sccheck: TOM-db2: Explorer finished. sccheck: TOM-db2: Starting single-node checks. sccheck: TOM-db2: Single-node checks finished. Press Enter to continue: >>> Autodiscovery of Cluster Transport <<< If you are using Ethernet adapters as your cluster transport adapters, autodiscovery is the best method for configuring the cluster transport. However, it appears that scinstall has already been run at least once before on this machine. You can either attempt to autodiscover or continue with the answers that you gave the last time you ran scinstall. Do you want to use autodiscovery anyway (yes/no) [no]? yes Probing..... The following connection was discovered: TOM-db1:ce3 - TOM-db2:ce3 Probes were sent out from all transport adapters configured for cluster node "TOM-db1". But, they were only received on one of the network adapters on this machine ("TOM-db2"). This may be due to any number of reasons, including improper cabling, an improper configuration for "TOM-db1", or a switch which was confused by the probes. You can either attempt to correct the problem and try the probes again or try to manually configure the transport. Correcting the problem may involve re-cabling, changing the configuration for "TOM-db1", or fixing hardware. Do you want to try again (yes/no) [yes]?
Probing ..... The following connection was discovered: TOM-db1:ce3 - TOM-db2:ce3 Probes were sent out from all transport adapters configured for cluster node "TOM-db1". But, they were only received on one of the network adapters on this machine ("TOM-db2"). This may be due to any number of reasons, including improper cabling, an improper configuration for "TOM-db1", or a switch which was confused by the probes. You can either attempt to correct the problem and try the probes again or try to manually configure the transport. Correcting the problem may involve re-cabling, changing the configuration for "TOM-db1", or fixing hardware. Do you want to try again (yes/no) [yes]? no >>> Point-to-Point Cables <<< The two nodes of a two-node cluster may use a directly-connected interconnect. That is, no cluster transport junctions are configured. However, when there are greater than two nodes, this interactive form of scinstall assumes that there will be exactly two cluster transport junctions. Is this a two-node cluster (yes/no) [yes]? Does this two-node cluster use transport junctions (yes/no) [no]? >>> Cluster Transport Adapters and Cables <<< You must configure at least two cluster transport adapters for each node in the cluster. These are the adapters which attach to the private cluster interconnect. What is the name of the first cluster transport adapter (help) [ce1]? Adapter "ce1" is an Ethernet adapter. The "dlpi" transport type will be set for this cluster. Name of adapter on "TOM-db1" to which "ce3" is connected [ce3]? What is the name of the second cluster transport adapter (help) [ce3]? ce3 Adapter "ce3" is an Ethernet adapter. Name of adapter on "TOM-db1" to which "ce5" is connected [ce5]?
Page 26
Wipro Confidential
>>> Global Devices File System <<< Each node in the cluster must have a local file system mounted on /global/.devices/node@<nodeID> before it can successfully participate as a cluster member. Since the "nodeID" is not assigned until scinstall is run, scinstall will set this up for you. You must supply the name of either an already-mounted file system or raw disk partition which scinstall can use to create the global devices file system. This file system or partition should be at least 512 MB in size. If an already-mounted file system is used, the file system must be empty. If a raw disk partition is used, a new file system will be created for you. The default is to use /globaldevices. Is it okay to use this default (yes/no) [yes]? n Do you want to use an already existing file system (yes/no) [yes]?y What is the name of the file system? /globaldevices2 >>> Automatic Reboot <<< Once scinstall has successfully installed and initialized the Sun Cluster software for this machine, it will be necessary to reboot. The reboot will cause this machine to join the cluster for the first time. Do you want scinstall to reboot for you (yes/no) [yes]? no You will need to manually reboot this node in "cluster mode" after scinstall successfully completes. Press Enter to continue: >>> Confirmation <<< Your responses indicate the following options to scinstall: scinstall -ik \ -C TOMLClust \ -N TOM-db1 \ -A trtype=dlpi,name=ce1 -A trtype=dlpi,name=ce3 \ -B type=direct \ -m endpoint=:ce3,endpoint=TOM-db1:ce3 \ -m endpoint=:ce5,endpoint=TOM-db1:ce5 \ Are these the options you want to use (yes/no) [yes]?
Page 27
Wipro Confidential
Do you want to continue with the install (yes/no) [yes]? Checking device to use for global devices file system ... done Adding node "TOM-db2" to the cluster configuration ... done Adding adapter "ce1" to the cluster configuration ... done Adding adapter "ce3" to the cluster configuration ... done Adding cable to the cluster configuration ... done Adding cable to the cluster configuration ... done Copying the config from "TOM-db1" ... done Setting the node ID for "TOM-db2" ... done (id=2) Verifying the major number for the "did" driver with "TOM-db1" ... done Checking for global devices global file system ... done Updating vfstab ... done Verifying that NTP is configured ... done Installing a default NTP configuration ... done Please complete the NTP configuration after scinstall has finished. Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done Adding the "cluster" switch to "hosts" in nsswitch.conf ... done Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done Verifying that power management is NOT configured ... done Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done Ensure network routing is disabled ... done Press Enter to continue: *** Install Menu *** Please select from any one of the following options: 1) Install all nodes of a new cluster 2) Install just this machine as the first node of a new cluster 3) Add this machine as a node in an existing cluster ?) Help with menu options
q) Return to the Main Menu Option: q *** Main Menu *** Please select from one of the following (*) options: 1) Install a cluster or cluster node 2) Configure a cluster to be JumpStarted from this install server * 3) Add support for new data services to this cluster node * 4) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: q Log file - /var/cluster/logs/install/scinstall.log.3241 Apply the recommended Sun Cluster Reboot patches & reboot the system in cluster mode. I.e. init 6
Page 29
Wipro Confidential
8.
Creating Metaset device (Device Group)
# scdidadm L 1 2 3 4 5 6 6 7 8 9 10 11 TOM-db1:/dev/rdsk/c0t0d0 TOM-db1:/dev/rdsk/c1t0d0 TOM-db1:/dev/rdsk/c1t1d0 TOM-db1:/dev/rdsk/c1t2d0 TOM-db1:/dev/rdsk/c1t3d0 TOM-db1:/dev/rdsk/c3t44d0 TOM-db2:/dev/rdsk/c3t40d0 TOM-db2:/dev/rdsk/c0t0d0 TOM-db2:/dev/rdsk/c1t0d0 TOM-db2:/dev/rdsk/c1t1d0 TOM-db2:/dev/rdsk/c1t2d0 TOM-db2:/dev/rdsk/c1t3d0 /dev/did/rdsk/d1 /dev/did/rdsk/d2 /dev/did/rdsk/d3 /dev/did/rdsk/d4 /dev/did/rdsk/d5 /dev/did/rdsk/d6 /dev/did/rdsk/d6 /dev/did/rdsk/d7 /dev/did/rdsk/d8 /dev/did/rdsk/d9 /dev/did/rdsk/d10 /dev/did/rdsk/d11
Identifiy the storage disk with same did for e.g in above output d6 is did no for storage # cfgadm al Ap_Id Type Receptacle Occupant Condition c0 scsi-bus connected configured unknown c0::dsk/c0t0d0 CD-ROM connected configured unknown c1 scsi-bus connected configured unknown c1::dsk/c1t0d0 disk connected configured unknown c1::dsk/c1t1d0 disk connected configured unknown c1::dsk/c1t2d0 disk connected configured unknown c1::dsk/c1t3d0 disk connected configured unknown c2 scsi-bus connected unconfigured unknown c3 fc-private connected configured unknown c3::256000c0ffc83df3 disk connected configured unknown c4 fc-private connected configured unknown c4::266000c0ffe83df3 ESI connected configured unknown usb0/1 unknown empty unconfigured ok usb0/2 unknown empty unconfigured ok usb1/1 unknown empty unconfigured ok usb1/2 unknown empty unconfigured ok
Page 30
Wipro Confidential
# metaset s TOM a h TOM-db1 TOM-db2 # metaset s TOM a /dev/did/dsk/d6 # metadb s TOM I 8.1. Created partitions and metadevices # metainit s TOM d50 1 1 /dev/did/dsk/d6s0 # metainit s TOM d60 1 1 /dev/did/dsk/d6s6
9. Adding Quorum Disk

To complete this procedure, identify a disk drive by its device ID (DID), which is shared by the nodes. 1. Login as root on TOM-db1 2. Run scsetup utility i. #scsetup ii. The main menu will be displayed 3. To work with quorum devices, type 1 (Quorum). The Quorum Menu is displayed. 4. To add a quorum device, type 1 (Add a quorum disk). Follow the instructions and type the name of the device to be used as the quorum device.(d6) 5. Verify that the quorum device has been added. # scstat -q
Page 31
Wipro Confidential
10. Installation Registration of Oracle HA agent
On TOM-db1 Install the SUNWscor on TOM-db1 and TOM-db2 data service package for Oracle 8 from Sun Cluster 3.1 Agent CD. Run # scsetup *** Main Menu *** Please select from one of the following options: 1) Quorum 2) Resource groups 3) Data Services 4) Cluster interconnect 5) Device groups and volumes 6) Private hostnames 7) New nodes 8) Other cluster properties ?) Help with menu options q) Quit Option: 2
Page 32
Wipro Confidential
*** Resource Group Menu *** Please select from one of the following options: 1) Create a resource group 2) Add a network resource to a resource group 3) Add a data service resource to a resource group 4) Resource type registration 5) Online/Offline or Switchover a resource group 6) Enable/Disable a resource 7) Change properties of a resource group 8) Change properties of a resource 9) Remove a resource from a resource group 10) Remove a resource group 11) Clear the stop_failed error flag from a resource ?) Help s) Show current status q) Return to the main menu Option: 1 >>> Create a Resource Group <<< Use this option to create a new resource group. You can also use this option to create new resources for the new group. A resource group is a container into which you can place resources of various types, such as network and data service resources. The cluster uses resource groups to manage its resource types. There are two types of resource groups, failover and scalable. Only failover resource groups may contain network resources. A network resource is either a LogicalHostname or SharedAddress resource. It is important to remember that each scalable resource group depends upon a failover resource group which contains one or more SharedAddress network resources. Is it okay to continue (yes/no) [yes]? Select the type of resource group you want to add: 1) Failover Group 2) Scalable Group Option: 1 What is the name of the group you want to add? TOML-RG
Do you want to add an optional description (yes/no) [yes]? Description: Oracle HA Resourse Group Because this cluster has two nodes, the new resource group will be configured to be hosted by both cluster nodes. At this time, you may select one node to be the preferred node for hosting this group. Or, you may allow the system to select a preferred node on an arbitrary basis. Do you want to specify a preferred node (yes/no) [yes]? Select the preferred node for hosting this group: 1) TOM-db1 2) TOM-db2 Option: 1 Some types of resources (for example, HA for NFS) require the use of an area in a global file system for storing configuration data. If any of the resources that will be added to this group require such support, you can specify the full directory path name now. Do you want to specify such a directory now (yes/no) [no]? Is it okay to proceed with the update (yes/no) [yes]? scrgadm -a -g TOML-RG -h TOM-db1,TOM-db2 scrgadm -c -g TOML-RG -y RG_description="Oracle HA Resourse Group" Commands completed successfully. Press Enter to continue: Do you want to add any network resources now (yes/no) [yes]? Select the type of network resource you want to add: 1) LogicalHostname 2) SharedAddress Option: 1 If a failover resource group contains LogicalHostname resources, the most common configuration is to have one LogicalHostname resource for each subnet.
Page 34
Wipro Confidential
How many LogicalHostname resources would you like to create [1]? Each network resource manages a list of one or more logical hostnames for a single subnet. This is true whether the resource is a LogicalHostname or SharedAddress resource type. The most common configuration is to assign a single logical hostname to each network resource for each subnet. Therefore, scsetup(1M) only supports this configuration. If you need to support more than one hostname for a given subnet, add the additional support using scrgadm(1M). Before scsetup(1M) can create a network resource for any logical hostname, that hostname must be specified in the hosts(4) file on each node in the cluster. In addition, the required network adapters must be actively available on each of the nodes. What logical hostname do you want to add? TOM-db Is it okay to proceed with the update (yes/no) [yes]? scrgadm -a -L -g TOML-RG -l TOM-db scrgadm -c -j TOM-db -y R_description="LogicalHostname resource for TOM-db" Commands completed successfully. Press Enter to continue: Do you want to add any additional network resources (yes/no) [no]? Do you want to add any data service resources now (yes/no) [yes]? Select the type of resource you want to add: Res Name ======== Description ===========
1) SUNW.Event HA Event server for Sun Cluster 2) SUNW.HAStorage HA Storage Resource Type 3) SUNW.HAStoragePlus HA Storage Plus - A Resource Type which sub ... 4) SUNW.RGOffload Offload Resource Group 5) SUNW.gds:3.1 Generic Data Service for Sun Cluster 6) SUNW.oracle_listener:3.1 Resource type for Oracle Listener 7) SUNW.oracle_server:4 Resource type for Oracle Server Option: 6 What is the name of the resource you want to add? TOML-LSNR Some resource types require that you set certain extension properties. Please check the man page for your data service to learn more about extension properties associated with the resource that you are adding.
This resource type does require that you set one or more extension properties. Select a property you would like to set: Property Name ============= 1) ORACLE_HOME 2) Listener_name 3) User_env 4) Debug_level 5) Probe_timeout q) Done Option: 1 Property name: ORACLE_HOME Property description: Oracle Home diectory Property type: string Property value: /oracle/product/8.1.6 Select a property you would like to set: Property Name ============= 1) ORACLE_HOME 2) Listener_name 3) User_env 4) Debug_level 5) Probe_timeout q) Done Option: 2 q Default Setting Desired Setting =============== =============== /oracle/product/8. LISTENER <NULL> 1 30 Default Setting Desired Setting =============== =============== <Needs Setting> LISTENER <NULL> 1 30
Are you done setting properties (yes/no) [yes]? Here is the list of extension properties you want to set: ORACLE_HOME=/oracle/product/8.1.6 Is it correct (yes/no) [yes]? Is it okay to proceed with the update (yes/no) [yes]?
scrgadm -a -j TOML-LSNR -g TOML-RG -t SUNW.oracle_listener:4 -x ORACLE_HOME="/oracle/product/8.1.6" scrgadm -c -j TOML-LSNR -y R_description="Failover data service resource for SUNW.oracle_listener:4" Commands completed successfully. Press Enter to continue: Do you want to enable this resource (yes/no) [yes]? scswitch -e -j TOML-LSNR scswitch -e -M -j TOML-LSNR Commands completed successfully. Press Enter to continue: Do you want to add any additional data service resources (yes/no) [no]? yes
Page 37
Wipro Confidential
Select the type of resource you want to add: Res Name ======== Description ===========
1) SUNW.Event HA Event server for Sun Cluster 2) SUNW.HAStorage HA Storage Resource Type 3) SUNW.HAStoragePlus HA Storage Plus - A Resource Type which sub ... 4) SUNW.RGOffload Offload Resource Group 5) SUNW.gds:3.1 Generic Data Service for Sun Cluster 6) SUNW.oracle_listener:3.1 Resource type for Oracle Listener 7) SUNW.oracle_server:4 Resource type for Oracle Server Option: 7 What is the name of the resource you want to add? TOML-ORA Some resource types require that you set certain extension properties. Please check the man page for your data service to learn more about extension properties associated with the resource that you are adding. This resource type does require that you set one or more extension properties. Select a property you would like to set: Property Name ============= 1) ORACLE_SID 2) ORACLE_HOME 3) Alert_log_file 4) Parameter_file 5) Connect_string 6) Connect_cycle 7) Probe_timeout 8) Debug_level 9) Wait_for_online 10) User_env n) Next > q) Done Option: 1 Property name: ORACLE_SID Property description: Oracle System Identifier (SID) Property type: string
Default Setting Desired Setting =============== =============== <Needs Setting> <Needs Setting> <Needs Setting> <NULL> <Needs Setting> 5 60 1 True <NULL>
Property value:
toml
Select a property you would like to set: Property Name ============= 1) ORACLE_SID 2) ORACLE_HOME 3) Alert_log_file 4) Parameter_file 5) Connect_string 6) Connect_cycle 7) Probe_timeout 8) Debug_level 9) Wait_for_online 10) User_env n) Next > q) Done Option: 2 Property name: ORACLE_HOME Property description: Oracle Home directory Property type: string Property value: /oracle/product/8.1.6 Select a property you would like to set: Property Name ============= 1) ORACLE_SID 2) ORACLE_HOME 3) Alert_log_file 4) Parameter_file 5) Connect_string 6) Connect_cycle 7) Probe_timeout 8) Debug_level 9) Wait_for_online 10) User_env n) Next > q) Done Option: 3
Default Setting Desired Setting =============== =============== toml <Needs Setting> <Needs Setting> <NULL> <Needs Setting> 5 60 1 True <NULL>
Default Setting Desired Setting =============== =============== toml /oracle/product/8. <Needs Setting> <NULL> <Needs Setting> 5 60 1 True <NULL>
Property name: Alert_log_file Property description: Oracle alert log file Property type: string Property value: /TOM-db/data2/toml/trace/bdump/alert_toml/ Select a property you would like to set: Property Name ============= 1) ORACLE_SID 2) ORACLE_HOME 3) Alert_log_file 4) Parameter_file 5) Connect_string 6) Connect_cycle 7) Probe_timeout 8) Debug_level 9) Wait_for_online 10) User_env n) Next > q) Done Option: 5
.log
Default Setting Desired Setting =============== =============== toml /oracle/product/8. /TOM-db/data2/toml <NULL> <Needs Setting> 5 60 1 True <NULL>
Property name: Connect_string Property description: Oracle user and password. Used by fault monitor to connect to database Property type: string Property value: sys/citirix8i Select a property you would like to set: Property Name ============= 1) ORACLE_SID 2) ORACLE_HOME 3) Alert_log_file 4) Parameter_file 5) Connect_string 6) Connect_cycle 7) Probe_timeout 8) Debug_level 9) Wait_for_online 10) User_env
Default Setting Desired Setting =============== =============== toml /oracle/product/8. /TOM-db/data2/toml <NULL> sys/citirix8i 5 60 1 True <NULL>
Page 40 Wipro Confidential
n) Next > q) Done Option: q Are you done setting properties (yes/no) [yes]? Here is the list of extension properties you want to set: ORACLE_SID=toml ORACLE_HOME=/oracle/product/8.1.6 Alert_log_file=/TOM-db/data2/toml/trace/bdump/alert_toml.log Connect_string=sys/citirix8i Is it correct (yes/no) [yes]? Is it okay to proceed with the update (yes/no) [yes]? scrgadm -a -j TOML-ORA -g TOML-RG -t SUNW.oracle_server:4 -x ORACLE_SID="toml" -x ORACLE_HOME="/oracle/product/8.1.6" -x Alert_log_file="/TOMdb/data2/toml/trace/bdump/alert_toml.log" -x Connect_string="sys/citirix8i" scrgadm -c -j TOML-ORA -y R_description="Failover data service resource for SUNW.oracle_server:4" Commands completed successfully. Press Enter to continue: Do you want to enable this resource (yes/no) [yes]? scswitch -e -j TOML-ORA scswitch -e -M -j TOML-ORA Commands completed successfully. Press Enter to continue: Do you want to add any additional data service resources (yes/no) [no]? no
Page 41
Wipro Confidential
Press Enter to continue: *** Resource Group Menu *** Please select from one of the following options: 1) Create a resource group 2) Add a network resource to a resource group 3) Add a data service resource to a resource group 4) Resource type registration 5) Online/Offline or Switchover a resource group 6) Enable/Disable a resource 7) Change properties of a resource group 8) Change properties of a resource 9) Remove a resource from a resource group 10) Remove a resource group 11) Clear the stop_failed error flag from a resource ?) Help s) Show current status q) Return to the main menu Option: s -- Cluster Nodes -Node name Status -------------Cluster node: TOM-db1 Online Cluster node: TOM-db2 Online ------------------------------------------------------------------- Cluster Transport Paths -Endpoint Endpoint Status -------------------Transport path: TOM-db1:ce5 TOM-db2:ce5 Transport path: TOM-db1:ce3 TOM-db2:ce3 ------------------------------------------------------------------- Quorum Summary -Quorum votes possible: 3
Path online Path online
Page 42
Wipro Confidential
Quorum votes needed: Quorum votes present:
2 3
-- Quorum Votes by Node -Node Name Present Possible Status --------------- -------- -----Node votes: TOM-db1 1 1 Online Node votes: TOM-db2 1 1 Online -- Quorum Votes by Device -Device Name Present Possible Status ----------------- -------- -----Device votes: /dev/did/rdsk/d6s2 1 1 Online ------------------------------------------------------------------- Device Group Servers -Device Group Primary Secondary [7m--More-- [m -------------------------Device group servers: TOM TOM-db1 TOM-db2 -- Device Group Status -Device Group Status ----------------Device group status: TOM Online -- Multi-owner Device Groups -Device Group Online Status ------------------------------------------------------------------------------------------ Resource Groups and Resources -Group Name Resources -----------------Resources: TOML-RG TOM-db DB-hastp-rs TOML-LSNR TOML-ORA
[7m--More-- [m [K -- Resource Groups -Group Name Node Name ---------------------Group: TOML-RG TOM-db1 Group: TOML-RG TOM-db2 -- Resources -Resource Name Node Name ------------------------Resource: TOM-db TOM-db1 Resource: TOM-db TOM-db2 Resource: DB-hastp-rs Resource: DB-hastp-rs Resource: TOML-LSNR Resource: TOML-LSNR [7m--More-- [m [K Resource: TOML-ORA Resource: TOML-ORA TOM-db1 TOM-db2 TOM-db1 TOM-db2 State Status Message -------------Online Online - LogicalHostname online. Offline Offline Online Online Offline Offline Online Online Offline Offline State Online Offline
TOM-db1 TOM-db2
Online Online Offline Offline
------------------------------------------------------------------- IPMP Groups -Node Name Group Status Adapter Status ------------- ------------ -----IPMP Group: TOM-db1 IPMP Online ce1 Standby IPMP Group: TOM-db1 IPMP Online ce0 Online IPMP Group: TOM-db2 IPMP Group: TOM-db2 IPMP1 Online IPMP1 Online ce1 ce0 Standby Online
Page 44
Wipro Confidential
Press Enter to continue: *** Resource Group Menu *** Please select from one of the following options: 1) Create a resource group 2) Add a network resource to a resource group 3) Add a data service resource to a resource group 4) Resource type registration 5) Online/Offline or Switchover a resource group 6) Enable/Disable a resource 7) Change properties of a resource group 8) Change properties of a resource 9) Remove a resource from a resource group 10) Remove a resource group 11) Clear the stop_failed error flag from a resource ?) Help s) Show current status q) Return to the main menu Option: q *** Main Menu *** Please select from one of the following options: 1) Quorum 2) Resource groups 3) Data Services 4) Cluster interconnect 5) Device groups and volumes 6) Private hostnames 7) New nodes 8) Other cluster properties ?) Help with menu options q) Quit Option: q
Page 45
Wipro Confidential
11. Enable HAStorage+ for Oracle Instance

scrgadm -a -t SUNW.HAStoragePlus scrgadm -a -j DB-hastp-rs -g TOML-RG -t SUNW.HAStoragePlus x FilesystemMountPoints=/TOM-db1, TOM-db2 scrgadm -a -g TOML-RG -j TOML-LSNR -t SUNW.oracle_listener -x LISTENER_NAME=LISTENER -x ORACLE_HOME=/oracle/product/8.1.6 -y Resource_dependencies=DB-hastp-rs scrgadm -a -g TOML-RG jTOML-ORA -t SUNW.oracle_server -x ORACLE_HOME=/oracle/product/8.1.6 -x Alert_log_file=/TOM-db/data2/toml/trace/bdump/alert_toml.log x ORACLE_SID=toml -x Connect_string=sys/citrix8i -y Resource_dependencies=DB-hastp-rs Checked DB Failover through sun Cluster scswitch z g TOML-RG h TOMdb2
12. Cluster Command for Failover testing

12.1. Starting the machine
For Cluster Mode

o Give the command ok>boot to start the machine in cluster mode. For Non-Cluster Mode o Give the command ok>boot -x to start the machine in non-cluster mode. Shutting down the machine
12.2.
To shutdown the cluster, give the following command on Primary node (TOMdb1)
o #scshutdown y g0
This command will bring down the secondary node first and then the primary node.
Page 46 Wipro Confidential
12.3.
Shutting down Single System in Cluster
To shutdown any node of the cluster, give the following command

o #init 0
12.4. Switching the resources from Primary node (TOM-db1) to Secondary node (TOM-db2)
#scswitch S h TOM-db1 #scswitch z g TOMLRG h TOM-db2

Stopping Oracle resources without shutting down the cluster services
12.5.
To shutdown Oracle Server resource, give the following command on TOM-db1

o o #scswitch n j TOML-ORA #scswitch n j TOML-LSNR Starting Oracle resources in the cluster services
12.6.
To enable/start Oracle Server resource, give the following command on TOM-db1

o o #scswitch e j TOML-ORA #scswitch e j TOML-LSNR
Page 47
Wipro Confidential
Page 48
Wipro Confidential

Sun Cluster Installation Guide With Oracle HA

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sun Cluster Installation Guide With Oracle HA

Uploaded by

Copyright:

Available Formats

SUN Cluster 3.

SUN Cluster 3.1Installation Guide

1. Installation of OS and Patches

SUN Cluster 3.1Installation Guide

2. Configuring Storage 3510

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

3. Creating and mounting of Volumes on server

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

5. Configuring IPMP for both the servers for failover

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

scinstall -ik \ -C TOMLClust \

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

Creating Metaset device (Device Group)

SUN Cluster 3.1Installation Guide

9. Adding Quorum Disk

SUN Cluster 3.1Installation Guide

10. Installation Registration of Oracle HA agent

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

Path online Path online

SUN Cluster 3.1Installation Guide

Quorum votes needed: Quorum votes present:

SUN Cluster 3.1Installation Guide

Online Online Offline Offline

SUN Cluster 3.1Installation Guide

SUN Cluster 3.1Installation Guide

11. Enable HAStorage+ for Oracle Instance

12. Cluster Command for Failover testing

For Cluster Mode

SUN Cluster 3.1Installation Guide

Shutting down Single System in Cluster

To shutdown any node of the cluster, give the following command

#scswitch S h TOM-db1 #scswitch z g TOMLRG h TOM-db2