This action might not be possible to undo. Are you sure you want to continue?
Step-by-step instructions for installing Microsoft Cluster Server, installing Oracle Fail Safe and configuring a database.
Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide
Microsoft Cluster Server and Oracle Fail Safe...........................................................................1 Quick Start Guide ...................................................................................................................1 Introduction ............................................................................................................................1 Part 1: Hardware Configuration and Set-Up .............................................................................1
Certified Hardware.......................................................................................................... 1 Disk Configuration.......................................................................................................... 1 Configure Network Cards ............................................................................................... 2
Part 2: Installing Microsoft Cluster Server ................................................................................5
Installing MSCS on the First Node ................................................................................. 5 Adding Additional Nodes ............................................................................................... 9 Using Cluster Administrator ......................................................................................... 10
Part 3: Installing Oracle Fail Safe.......................................................................................... 11
Match Home Names on All Nodes ............................................................................... 11 Oracle Services for MSCS Security Setup .................................................................... 12 Completing the Fail Safe Configuration....................................................................... 13 Making the Database Fail Safe ..................................................................................... 14 Creating the Database ................................................................................................... 15 Verifying the Standalone Database Configuration ....................................................... 16 Creating a Group ........................................................................................................... 17 Adding the Database to a Group ................................................................................... 22
com/hcl/ Disk Configuration Disks need only be configured from one node. Instead. so the entire disk must always move together. Install Oracle Fail Safe Part 1: Hardware Configuration and Set-Up Certified Hardware Oracle does not specifically certify hardware for Oracle Fail Safe. Part One provides you the hardware configuration. and open the Disk Management Console Partitioning a single physical disk into multiple partitions can be done. it normally makes sense to simply create one partition on each Physical Disk.microsoft. Note. Install Cluster Server on First Node and on Second/Additional Nodes 3. Part 3 gives you the step-by-step instructions for installing Oracle Fail Safe and configuring a database. 1 .Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Introduction This paper is divided into two parts. Choose a node from which to configure the disks. Do not attempt to write to the disks from multiple nodes until the clustering software has been installed. prior to configuring the disks in the Disk Management console. Here is an overview of the steps required to install MSCS: 1. Format all of the shared drives as NTFS volumes and assign the drive letters as appropriate. Avoid creating software volumes—any striping or RAID configuration should be done at the hardware level. no matter how many partitions are on it. but MSCS sees the entire Physical Disk as a single resource. you must ensure that the hardware is on the Microsoft Cluster Server Hardware Compatibility List (HCL) that is available from Microsoft? . this will give you better performance. You will find the HCL at: http://www. Part Two provide you the step-by-step instructions for installing Microsoft Cluster Server (MCS). Hardware Configuration and Set-Up ? Confirm Hardware is Certified for MSCS ? ? Configure Shared Disks ? ? Select Disk to be Quorum Disk ? ? Configure Network Cards ? ? Obtain IP Address and Network Name for Cluster Group and Register in ? DNS or HOSTS file 2. Therefore. in the example below that we have labeled volumes as either Shared or Private.
the cluster fails. Configure Network Cards It is likely that you will have at least two network cards in each node of the cluster. It is possible to have the cluster communications go through the public network. The quorum disk does not require much space. Decide which shared disk you want to be the quorum disk. therefore you may want the quorum disk to be a RAID volume of some type. you can go through a hub if you have more than two nodes. It is possible in some versions. to place Oracle datafiles on the same drive as the quorum disk. so you should choose the smallest drive possible. Or. If there are only two nodes in the cluster. One network card is generally used for public communication with network clients and servers. but this is not recommended because the cluster communication involves polling of 2 . Additionally. Microsoft recommends a minimum drive size of 500MB. while the second network card is generally reserved for cluster communications.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Figure 1: Screenshot of the Computer ManagementConsole Quorum Disk MSCS requires that one of your shared disks be assigned as the quorum disk. it provides an area of physical storage that all nodes can access. The quorum disk is critical to resolving ownership of resources should the interconnect go down. Oracle and Microsoft recommend that the quorum disk be kept separate from any other resource disks. these cards can be connected directly to each other via a crossover cable. The quorum disk assists in handling certain clustering functions. Keep in mind that if the quorum disk fails.
if a listener is configured to listen on a host name. Look in the Adapters and Bindings tab and ensure that the card with your public IP address is first in the list. Thus. This is critical in ensuring the name resolution works correctly. but a network glitch could be incorrectly interpreted as a resource failure which could result in a restart or failover of a healthy resource. 2. If it is not listed as the first entry move it up. leaving the network card for the interconnect bound last of all. How to Check the Binding Order 1. you may see that a ping of the public host name resolves to the private IP address. From the Advanced drop-down menu. Not only can this polling result in a large amount of traffic. Any public cards which will be communicating with client machines should always be bound first. and a second card dedicated to the public network. it is better to have a dedicated network for the resource polling. Thus. 3. choose Advanced Settings.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide resources on a regular basis. Right-click My Network Places and choose Properties. 3 . Binding Order With a network card dedicated to the interconnect. it is important to ensure that the bindings are set up correctly. particularly when nodes are communicating with each other. it may incorrectly resolve that host name to the private IP address which means incoming connections from clients will fail. If the binding order is incorrect. Follow the same steps on both nodes.
Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Figure 2: Screenshot of the Adapters and Bindings Window Disabling WINS on Interconnect You also want to ensure that the WINS address is left empty for the private card. Be sure to include the IP addresses and host names for groups that you intend to create for the cluster itself as well as any Fail Safe groups. Choose the Advanced button and select the WINS tab. 1. Choose Properties. make sure that all public IP and host name combinations have been registered in DNS. remove it otherwise the Cluster Service will become confused when attempting to communicate with the Domain Controller (all cluster nodes must be members of a domain). Additionally. and select Properties again for the Internet Protocol (TCP/IP). 2. If there is a WINS address defined. 3. Use DNS or HOSTS for Name Resolution Finally. Right-click the private network connection in Network and Dial-up Connections. you may want 4 .
You will be prompted for the Windows 2000 Advanced Server CD. you have all of the necessary host names and IP addresses registered in DNS or in the HOSTS file. Choose Add/Remove Windows Components from the dialog window. Verify that a ping of the public name always returns the public IP address.10. and you have confirmed that your network cards are configured appropriately. C:\>ping rmntofs1.10.2 192.SAN RMNTOFS1 RMNTOFS2 RMNTCLUSER RMNT_FAIL-1 #PRIVATE CONNECTION for Node1 #PRIVATE CONNECTION for Node2 #PUBLIC Connection for Node1 #PUBLIC Connection for Node2 #MSCS Cluster Group IP #Fail Safe Group IP Double-check the setup by pinging the public and private names of all nodes in the cluster.1 192.1 10. 2.SAN" to the end of the actual node name. Place a check box next to Cluster Service and choose Next.. Open up the Windows 2000 Control Panel on one of your cluster nodes. and use that as the host name assigned to the private card. and then the Cluster Configuration Wizard will be started.1: bytes=32 time<10ms TTL=128 .1.10.. Part 2: Installing Microsoft Cluster Server Once you have all of the hardware properly set-up and configured: your disks are partitioned such that you have enough physical drives to support the appropriate number of groups.ORACLE.10.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide to assign a network name to the cards on the private interconnect.SAN RMNTOFS2. you are now ready to install Microsoft Cluster Server.1.US.1. 5 .1. and choose Add/Remove Programs.3 192. A popular naming convention is to append ". and a ping of the private name returns the private IP address: C:\>ping rmntofs1 Pinging rmntofs1.1.4 RMNTOFS1. 3.1.1. using the private interconnect.1. Since these cards usually are not going to be connected to a DNS server.10.san Pinging RMNTOFS1.2 192. Installing MSCS on the First Node 1. ping each node from itself. You can find the hosts file in the \WINNT\System32\drivers\etc directory. If you have two nodes called RMNTOFS1 and RMNTOFS126.96.36.199: bytes=32 time<10ms TTL=128 .1.1. your host file entries might look like so: 10.10.1.10.COM [192. you should add entries into the hosts file.1] with 32 bytes of data: Reply from 10.SAN [10.1] with 32 bytes of data: Reply from 192. This convention indicates clearly that this hostname is on its own subnet.
This is a Domain Administrator Account. this step will fail. Click the I Understand button and choose Next. 6. Continue to the next screen. On the next screen. where you will choose which drive will be the quorum disk. and the domain name that the cluster node is a member of should show up in the bottom box. Notice the disclaimer states that hardware not on the HCL is not supported. 7. If not.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide 4. Figure 3: Screenshot of the Cluster Name Dialog Window User Account Set-up for Running Cluster Service 8. (You will be prompted for the IP address later on in the install. Ensure that all of the drives that you intend to use are listed on the right-hand side. Type in the correct username and password and continue on to the next screen. this network name and cluster IP combination should have already been registered in DNS or in the hosts file. Indicate this is the first note in the cluster. On the Add or Remove Managed Disks window you should see the listing of shared drives that you previously configured in the Disk Management Console. 6 . Choose Next on the welcome screen to display a link to the Microsoft Hardware Compatibility List (HCL).. you will be prompted for a username under which the Cluster Service will run. Input the network name that you have chosen for the Cluster Group. Remember. under the Managed Disks column.) 5. 9.
the public network will be configured only as a fallback.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Figure 4: Screenshot of the Cluster Name Dialog Window Defining Networks 10. 12. so that a second private network can be defined for the interconnect. assuming that both networks are functioning. If you have more than two cards in each node. you want to ensure that you select the radio button to enable the network for Internal Cluster Communications Only. 11. you will be prompted to enter the IP address that you have reserved for the virtual Cluster Group. this IP 7 . For the final step. For the public network. For the "Private" network. As previously mentioned. configure the networks according to which order you want cluster communications to fall back in the event of a failure. After selecting the quorum disk. you will determine which network should be used first for cluster communications. to provide a certain amount of redundancy. you should probably select All Communications. again providing additional redundancy. we recommend that you keep it simple and call them "Public" and "Private". It is also fairly common for some sites to have three or four network cards in each node. you will be presented with a screen on which you will define the networks. You can name them whatever you choose— generally. so that as long as it is functional. Be sure that the Private network is first. On the next screen.
144. Type in the IP and ensure that the correct network is chosen.1.117. the cluster name is RMNTCLUSER. On the final screen. be sure to click Finish to complete the cluster installation. and the IP Address is 138.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide address is the same that was registered in DNS or the HOSTS file with the cluster’s Network name that was specified at the outset of the MSCS install. Figure 5: Screenshot of the Cluster IP Address Window 8 . In our example.
Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Adding Additional Nodes The process of adding an additional node to the cluster is much quicker. select the radio button for The Second Or Next Node In The Cluster. On the second node. Provide the same username. Figure 6: Screenshot of the Create or Join a Cluster Window 9 . start the install in the same fashion as before. and then finish the cluster installation on the second node. but this time. password. and domain information as in the initial install. This node has now joined the cluster as an equal member.
and the quorum disk. you will be able to delete the disk group. Initially. you see in the Figure that you will have a Disk Group for each additional shared disk besides the quorum disk. You cannot add an Oracle database or other resources to this group—you must create a second group. you will have a group called "Cluster Group". ownership of the disk groups can still be transferred back and forth between the nodes. you will be able to run the Microsoft Cluster Administrator to view the nodes. Figure 7: Cluster Administrator Disk Groups In addition to the Cluster Group. This is the first virtual server group that has been created as part of your cluster. groups. Start Cluster Administrator by clicking Start | Programs | Administrative Tools | Cluster Administrator. the install of Fail Safe later on will add an Oracle Fail Safe Server into the Cluster Group. These Disk Groups are simply placeholders for the disk resources—they are not true virtual groups. and resources in your cluster. However. as they do not have network names and IP addresses associated.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Using Cluster Administrator Once you installed Microsoft Cluster Server. The Figure below is an expanded view of Cluster Administrator. the disk resource associated will be removed from the temporary disk group and placed into the database group. 10 . after a fresh install. if you so desire. the Cluster Name. 1. When a database with files residing on one of these disks is added to a new group. We discuss this in the coming section on Fail Safe installation. However. which contains as resources the Cluster IP Address. At this time.
you must make sure that the home names match identically for each of these products on all nodes in the cluster. you may not want or need all of the software on all of the nodes in the cluster. In addition. Thus. After selecting the home name and directory. Choosing a Typical install will give you the components necessary to make the database highly available.select Oracle Fail Safe. This is primarily a consideration in clusters with multiple nodes. Part 3: Installing Oracle Fail Safe As mentioned earlier. As such. separate from other Oracle products. you are ready to begin the actual install of the product. comprising different tiers. respectively. Second. 11 . In addition. Though this is not strictly required. you must ensure that you have enough space available on the private drives of all nodes in the cluster. planning an architecture with three or four nodes. When this is highlighted. You will also see a folder called Resources. if you are installing Fail Safe 3. and directories. Determine which nodes should be able to run the database and which nodes should be able to run the application software. Oracle software must be installed on the private drive on each node of the cluster. If you are. During the install of Fail Safe. on Node1 if the database software is installed in a home called OraHome90. the install must be performed as a user account with Local Administrator privileges on each node. We recommend that you install the Fail Safe software last. Once you have decided on the Oracle product choices. under Cluster Configuration you should see a Resource Types folder. Oracle Fail Safe should be installed into its own Oracle home. you will be cautioned that a reboot is required after the installation completes. this also requires proper planning prior to embarking on the installation.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Resources and Resource Types Refer again to the Figure 7 the Cluster Administrator. and plan accordingly. or 9iAs) and Oracle Fail Safe itself. Reports. you will be prompted to select either Oracle Fail Safe or Real Application Cluster Guard. any Oracle application software (such as Forms. the group in which each resource resides. We also recommend that you match the directory names and orders of install on all nodes when possible. When highlighted. it will list all cluster resources. this will list each of the resource types and the Resource DLL used to monitor that type of resource. and the current owning node. Again. Prior to the actual beginning of the installation. home names. the Cluster Service must be running. you must determine which nodes in the cluster are meant to run which software. Once Oracle is installed and configured. This includes the database software. . you should see a resource type of Oracle Database listed here. and Fail Safe itself is installed in a home called OFSHome. Match Home Names on All Nodes It is required that the Oracle home names for the database software and the Fail Safe software. in fact. it prevents confusion and simplifies administration. First.2 (the first release to be certified with Oracle9i). are identical on each node.
Again. username. at HKLM\Software\Oracle\Fail Safe. You should use the same account for all nodes.2. repeat the preceding steps on each node of the cluster. so starting with the 3. rebooting each node after the Fail Safe install completes. you may experience a hang when running the Verify Cluster tool unless SYSTEM is explicitly added to the default access permissions. This can be the same account information that you provided earlier for the MS Cluster Server installation. Running the Security Setup Post Install Should the need arise to change passwords after an install.1 for more details on this problem.1. nullifying any default permissions.x and lower. Reboot Each Node Independently after Install After Fail Safe has been installed on the first node. However. In addition. the Oracle Services for MSCS Security Setup has been modified to always add the SYSTEM account. and must also have Local Administrator privileges on all nodes of the cluster. Then. you will be prompted for another domain name. This is normally empty. At the end of the installation. See MetaLink Document ID 155317. Registry Keys Updated The Oracle Fail Safe install will add a Registry key as a subkey of the normal Oracle key. it must be rebooted. Starting with release 3. this service was named the Oracle Fail Safe service. This is the account that will be used to run the OracleMSCSServices. If default permissions are modified. Wait until the reboot completes and the node has rejoined the cluster prior to beginning the install on the second node. and thus the SYSTEM and INTERACTIVE accounts are assumed to have privileges. the security setup will configure DCOM access by calling the configuration tool and adding the local SYSTEM account to the default access permissions list for Distributed COM security. an Oracle key is created under the 12 . and password combination. but it does not have to be.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Oracle Services for MSCS Security Setup In Fail Safe releases 3. some third-party applications may add user accounts to the default access list. In earlier releases of Oracle Fail Safe. The account that you specify must be a Domain User on the same domain as MSCS uses.2 release. Any post-installation changes that you make with this tool will not take effect until after the OracleMSCSServices service is restarted. this service is named OracleMSCSServices. the Oracle Services for MSCS Security Setup can be run after the install by choosing Start | Programs | Oracle – <OFS Homename> | Oracle Services for MSCS Security Setup. the default access permissions were left untouched. or to update the security. You can view this by running dcomcnfg at a command prompt and choosing Default Security and editing Default Access Permissions. DCOM Security In addition to configuring the service logon. the service created by the Fail Safe install was called the Oracle Fail Safe Service. in prior releases. The Security setup will configure the OracleMSCSServices service to be started and run as the user that you specify.
In addition. of course. and so on. it will be actively running only on the node that owns the Cluster Group. and the install will do this for you. Fail Safe Manager provides invaluable troubleshooting tools to verify the cluster setup and resource configuration prior to adding resources to a group. you should uninstall it if possible. However. and that also has local administrative privileges.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide cluster key at HKLM\Cluster\Oracle. forcing you to reregister the Fail Safe resource types after you reinstall Fail Safe. This can be accomplished by rerunning Verify Cluster. The Cluster name and Domain name are. All of these operations can be done through Cluster Administrator as well. change dependencies and failover policies. you must provide an operating system account that is a member of the cluster’s domain. Fail Safe Manager duplicates some of the things that you see in Cluster Administrator. When logging in to Fail Safe Manager. Logging in to Fail Safe Manager Fail Safe Manager is the interface provided by Oracle to interact with the cluster. and to verify the integrity of a group after it has been created. you will be able to view this under HKLM\Cluster\Resource Types. so failure of this service will lead to a failure when logging on to Fail Safe Manager. discussed in the next section. Though the service exists on each node. which was created when you initially installed Microsoft Cluster Server. This service is a resource that gets added to the Cluster Group. the same as specified when installing the cluster: 13 . If you ever need to remove Fail Safe from a cluster. Last. Fail Safe Manager must be used to add an Oracle database or other supported Oracle resources into a Fail Safe group. the install of Oracle Fail Safe creates a service called OracleMSCSServices. Uninstalling Cluster Server will remove the HKLM\Cluster key. and it can be used to create new virtual groups. once the Oracle Database and Oracle TNS Listener resource types are registered. This is the process that Fail Safe Manager attaches to when it is run. Completing the Fail Safe Configuration As noted previously. This is the only Oracle resource that should be added to the Cluster Group. so that the resource types are unregistered and removed from the Registry. It can be used to monitor the location and ownership of resources.
e. these are the steps that you will follow: 14 . Heed Warnings in Verify Cluster Because Verify Cluster must complete in order to register the Resource DLL. you do not have to upgrade all at once. Once the Verify Cluster operation completes.2. and also to confirm that the Oracle install was done properly (i.x clusters and 3. Some errors/warnings are only informative in nature. This tool must be run to register the Oracle Resource DLL and Oracle Resource Types for use by the cluster. you will be given the choice to run the Verify Cluster tool or exit. However.2 release of OFS. Running Verify Cluster Run OFSM by choosing Start | Programs | Oracle – <OFS Homename> | Oracle Fail Safe Manager.1. a condition that may lead to name resolution problems and resource failures down the road.1 or later. However. and then rerun the Verify Cluster operation. Essentially. Refer to the earlier section on cluster configuration to resolve these problems. The first time that it is run on a new cluster. the home names and products installed match on each node). You should save the output from the clusterwide operation to a text file and check this file closely for any errors. and it will work with the 3. you are now ready to create the Fail Safe group and add a database. Making the Database Fail Safe Once Fail Safe has been successfully installed and the cluster setup has been verified. beginning with the 3.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Figure 8: Connect to Cluster Login Fail Safe Manager can be installed on a client machine to allow you remote management access to the cluster. you will not get an absolute failure message—you will almost always read that the operation completed successfully. in an environment with multiple clusters. if you see errors indicating an IP address mismatch. If you mistakenly name the Fail Safe home or the database home incorrectly on one of the nodes. this is an indication that the binding order of your cards is incorrect. you will need to reinstall in order to get Fail Safe to work properly. Thus. the Fail Safe Manager can be used to manage clusters running Fail Safe version 3. you should be able to see the Oracle Database and Oracle TNS Listener resource types listed in Cluster Administrator. However. You should also pay close attention to any errors reporting a mismatch in the names of the ORACLE_HOMEs on the respective nodes.x clusters. you may get warnings. Simply ensure that you have the latest version of Fail Safe Manager on your desktop. Verify Cluster checks the cluster configuration to make sure that all of the networking components are properly configured. Verify Cluster is the first of the "Verify xxx" operations provided by Fail Safe Manager to assist in configuration and assurance of the integrity of the database. nor do you need to sacrifice the manageability of using Fail Safe Manager to manage multiple clusters.1.. However. in addition to doing this. Previous releases of Oracle Fail Safe required that the Fail Safe Manager client be the same version as the Fail Safe Server running on the cluster. indicating that certain software components are not installed.
if you have an Active/Active configuration. this is meant more for demonstration purposes than as a template for your production instance. Oracle Fail Safe provides a template for a sample database. So while you can use this to quickly create a database to show the concept works. you must also determine if you are going to have the init file or spfile reside on the private drive or on the shared drive. this reduces the flexibility to have differences in certain parameters. depending on your needs and the available resources. you should put the parameter file on the shared drive. Move all drives where files will ultimately reside. but be sure when creating the database that all files associated with the database are on a shared drive. As a general rule. Having an alert log that is written to the private drive can lead to gaps in the log file if the group moves to another node in the cluster. depending on which node the database resides on. However. This includes control files. Placement of Parameter File In addition to placement of trace files. log files.ora on all nodes. you may need to consider having different parameter files. and any local archive destinations that you define in the init. since you do not have to be concerned with maintaining multiple copies of init. With an Active/Passive scenario.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide ?? Create the database ?? Verify the standalone database ?? Create the Virtual Group ?? Add the database to the group In this section. While it is not required to have the background_dump_dest and the user_dump_dest on shared drives. we detail each of these steps.ora (or SPFILE). we strongly recommend it. To do this. In a three. we recommend that you use the DBCA or your own scripts to create the true database. You should create the database on one node only. Note: If using an SPFILE. datafiles. Creating the Database If you have not yet created the database. In addition. Having the parameter file on the shared drive will ease administration. You cannot pass the SPFILE directly to Fail Safe when adding the database to a group. Place the parameter file accordingly. and what resources would be available to the database on each node in event of a failure. placed on the private drive of each node. and create the database from that node. you will have to determine which nodes the database will reside on. so that they are all owned by the same node. 15 . you can do so via the Database Configuration Assistant or you can create a database manually.or four-node cluster. you will have to have a normal init file with the line SPFILE=xxxx. However. which you can create through Fail Safe Manager itself. choose Create Sample Database from the Resource menu in Fail Safe Manager.
providing there is a service for the instance on that node (OracleService<sid>). and there is a valid TNSNAMES. Under Standalone Resources. Expand the node on which the database exists. An existing database will be discovered as a resource on the node where it resides. and then you should see a listing of Oracle resources on that machine that are supported in a Fail Safe environment. you should be able to discover it as a standalone resource on the node on which it was created. which connects to the same SID name or SERVICE_NAME. using the HOST name or IP address of the node: Figure 9: Screenshot of Oracle Fail Safe Manager 16 .Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Verifying the Standalone Database Configuration Once the database has been created. Fail Safe Manager will list the Nodes in the left-hand pane.ORA entry on the node. you will see a message that Fail Safe is "Discovering Standalone Resources" on the node. and you will see a folder for Groups on that node. and another folder for Standalone Resources.
At this point. these files must be reconfigured on each node to account for the virtual server connect information. Type in the name and an optional description and choose Next: 17 . Creating a Group We reiterate here that you cannot add the database into the Cluster Group—you must create a separate group for the database. and the services will be deleted from the other node(s). and whether you want to connect using OS Authentication or you want to provide a password. since the database is still a standalone database.ora files and ensure that they are configured correctly.ora and listener. because when the database is ultimately added to the group. and you must have a host name and IP address combination ready. Even though you can use MS Cluster Administrator to create the group. In addition. The Verify Standalone operation will also check to ensure that the services for the instance exist on only one node. we recommend that you create it through Fail Safe Manager. In Fail Safe Manager. parameter file location. it need not match the hostname. right-click it and choose Verify Standalone Database. you will be prompted for the correct node. so running Verify Standalone Database is an important step in ensuring these files are set up correctly and ready for the impending Add to Group operation. This is critical. If the database is configured for Automatic Startup or Shutdown. It will check that all drives being used by the database are shared drives. Failures in parsing these sqlnet configuration files is one of the most common reasons that an operation to add the database to a group will fail. This allows members to connect only to this particular instance—Fail Safe will not automatically create the more generic ORA_DBA group. If you choose OS authentication.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Once you identify your database. Why Run Verify Standalone? The Verify Standalone Database will check the configuration of the database and prepare it to be added into a Fail Safe Group. You will be prompted for a name for the group—this can be any name that you decide on. the services for the instance should not yet exist on the second node—if they do. because once in the group. those features will be disabled. Fail Safe will create a local OS group called ORA_<sidname>_DBA and add the accounts that were specified for the Cluster Service and the OracleMSCSServices. the Cluster Service will be responsible for bringing the database offline and online. as it provides an interface to add a hostname and IP address into the group. You will be prompted for the instance name. the Verify Standalone Database operation will check the tnsnames. rightclick the Groups folder and choose Create. but it will work if you manually add the accounts to this group instead of a group specific to your SID. in order to allow them to be parsed by Fail Safe when it comes time to add the database to a group.
Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Figure 10: Step 1 Creating a Group 18 .
do you want this group to back to the original node automatically? If so. Choosing Prevent Failback on Page 2 implies that there is no preferred node. then the group will not fail back automatically— you will need to manually move the group back to the preferred node if so desired. Adding a virtual address to the group accomplishes the same thing for your virtual server. Adding Virtual Addresses to a Group Once the group is created. and the original node then comes back online. and you must configure the server with that information. Think of this process as like adding an entirely new server to your network. this Failback event will be triggered as soon as the preferred node comes back online. you will be prompted to define a Failback Policy for the group.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Defining a Failback Policy and a Preferred Node On Page 2 of the Create Group Wizard. because the Failback is triggered when the preferred node rejoins the cluster. you will be immediately prompted to add a virtual address to the group. you must have an IP address and network name that are valid for your network. If the group fails over to the other node. so you will not see Page 3 of the Create Group Wizard. Accordingly. Figure 11: Step 2 Creating a Group A Failback policy does not have any meaning if there is not a preferred node. or should it happen only during specific hours? If you choose the Prevent Failback option. which is where the preferred node for the group is selected. how quickly? Should it happen immediately. if you chose to Failback Immediately. In order to bring up a new server on your network. A virtual address is simply an IP address and network name combination that will be assigned to the group that you have just created. which is associated with your 19 .
You will be prompted to select which network you want to add the virtual address from.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide newly created group—the wizard configures the group with that address. this network name and IP address combination must be unique on your network. In most cases. to provide further redundancy and load balancing. As an aside. it is possible to have multiple IP address and network name combinations existing in a single group. and it is also possible to have these IPs be on different subnets. which allows your clients to access the network. Theoretically. and it must resolve successfully and be accessible by any clients that wish to access the database. though. However. This virtual address then becomes the means by which your clients connect to the virtual server and communicate with the rest of the resources that will ultimately be added to this group. having two IP addresses in a group that are on different subnets would 20 . Thus. a virtual IP address must always be on the same subnet as at least one physical card within the cluster. if the only client is an application tier. and then MSCS is responsible for registering that address with the gateway and directing all network communications to the appropriate owning node. you could select the private cluster network. As such. even among other virtual address that already exist. and the Add Resource Wizard will be initialized. which runs on one of the other cluster nodes. Figure 12: Step 3 Creating a Group The network name and address that you supply must be valid on one of the subnets tied to a physical card. Choose Yes in answer to the Add Virtual Address question. you will be choosing the public network.
each with an IP address on the respective subnets used by the virtual IP.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide require two different physical network cards. 21 .
this time selecting a new network name and IP address combination not currently in use anywhere on your network.. the steps will be the same—be sure the appropriate Resource Type (Oracle Database) and group name are highlighted on the first page of the Add Resource to Group Wizard: : Figure 13: Step 1 Add a Resource Group 22 . and then put in the host name that you have predefined in DNS or your hosts file. the IP address should be filled in automatically. you will get an error indicating that the host name does not resolve to an IP address. Adding the Database to a Group Once you have completed the steps of successfully verifying the cluster setup. Duplicate network names. but it will not have a virtual address assigned. choosing Add Resource to Group. under Standalone Resources on the given node. and then selecting Oracle Database for the Resource Type. right-click the empty group. this will fail with an FS-11221 error. of course. you are ready to add your database into the group. and choose Add Resource to Group. and creating a group with a virtual IP address and host name combo. or by right-clicking the newly created group. are not allowed.. Another common error here is to put in the existing host name of the Cluster Group. indicating that this network name is already in use.. If this is set up correctly. However you start the process. You can do this in a couple of ways—by right-clicking the database itself.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Choose the appropriate network for the initial virtual IP. The group will still be created. You must then go back to Fail Safe Manager. If not.. The Add Resource Wizard will be initiated again. creating and verifying a standalone database. If you do so. and you can choose Virtual Address from the list of available Resource Types.
This is recommended if you want to allow access via the password file. continue on to the next screen. (Internal is still offered as an option for backward compatibility. you will still be asked if you want to maintain a password file on all nodes of the cluster.) The key thing to realize here is that if you do not use OS authentication.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Once you have verified this information. If you previously ran the Verify Standalone Database procedure and specified that you wanted to use OS authentication at that time. you will define the network service name. then you will be asked again. The polling that is done by the Cluster Service uses 23 .0 databases.) If you choose OS authentication here. If you had done this during the Verify Standalone operation this group will already exist. (Refer to Chapter 4 for more information on using a password file. the database name (as defined by DB_NAME in the init file). the instance name. then it is assumed that you are doing so again when the database is actually added to the group. and the logon accounts for both the Cluster Service and the OracleMSCSServices will be added to this group. and the location of the parameter file that you wish to use. but you do not want to add certain OS users to the ORA_DBA group. an OS group called ORA_<sidname>_DBA will be created. Figure 14: Step 2 Add a Resource Group The next page is the Database Authentication page. If you have not run Verify Standalone previously. because the 3. Here. Next. then you must ensure that any changes to the password file are propagated to all nodes in the cluster. again.2 release of Fail Safe Manager will support Oracle8i and Oracle 8. or if you chose to use the SYS account for authentication.
Once this is done. In addition. This will cause a second listener service to be created on the current node. the polling may fail.e.ora file will be updated to reflect the virtual host information for the group. or the database may not be able to come online at all. the entire group will be brought offline and moved to the other node(s) defined as possible owners. Fail Safe will create a service for the instance (OracleServicePROD90) and configure the tnsnames. and if the password is wrong on one of the nodes. The listener name will be FSLxxxx. Figure 15: Adding Resources 24 . where xxxx is the virtual host name associated with the group. When this operation is complete. the tnsnames. the database is now running in a Fail Safe environment.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide this information to connect. The service for your instance (i. which will be set to manual start also. or it will go back to the original node if a preferred node is not defined for the group. if it is not already. it will then actually bring the database online on that node. the group will be returned to reside on the preferred node. and a second listener will be added to listener.ora. the process to add the database to the group will begin. to confirm that all is configured correctly.. Once these changes are made. Behind the Scenes When Adding a DB to a Group Once you have answered the questions on database configuration and authentication.ora files on the subsequent node. OracleServicePROD90) will be set to manual start.ora and listener.
If the restart fails three times. Once connected. The Cluster Service will actually log on to the database using a sqlnet connect string. using information provided to it by the Oracle Database Resource DLL. Note: If you are forced to run both production and test databases in the same group. then an error is logged in the Application Log in the Windows 2000 Event Viewer. On the right. Fail Safe will attempt to stop and then restart the database on the same node. If four attempts to log on and run the query have failed. These checks are actually performed by the Microsoft Cluster Service. to ensure that it is still running. then the restart policy’ ‘Restart Policy’ should be left uppercasedefined for the database will kick in. or the query fail. due to a lack of disk resources or other limitations.Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide Behind the Scenes with a Fail Safe Database Once a database has been made Fail Safe.NAME=’SYSTEM’. An internal retry is executed three more times before the resource is officially considered to have failed. the following query is run: Select NAME from TS$ where TS$. you may want to consider removing the check from this box for your test database. so that a failure of a test instance will not affect the entire group. The “Is Alive” interval is a more thorough check. The Looks Alive interval is the shorter period of time. These retries after an error are normally executed within 15 seconds or less—this interval is internal and not configurable. the entire group should be affected. it is directed to retry using a local bequeath connection. Expand the group in Fail Safe Manager and select the recently added database. By default. then a failover to another node is initiated because the defined Failover Policy has determined that if this resource fails. If the logon fails. 25 . This is just a basic check to verify that the database is running. then once the resource has failed to restart the specified number of times. every 60 seconds a login to the database is completed and a query is run. By default. If this box is not checked. it will be marked as Failed and will be left alone. choose the Policies tab. we can begin to explore some of the resource properties to determine just exactly what is going on. Should the connect attempt fail. this is the interval at which the service for the instance is checked.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.