This lesson shows how to add a single-instance database to a group. When you add a single-instance database to a group, you make that database highly available. If the node on which the database is currently running is taken offline or fails, the database is restarted on a surviving cluster node.
In this lesson, you will add the sample database that you created in Creating a Sample Single-Instance Database to Group 1 group.
Select the resource you want to add to a group, then select Add Resource action from the Actions menu of the Oracle Resources view. Or right-click the selected resource in the Available Oracle Resources group to select Add Resource from the Available Oracle Resources actions.
The Add Resource to Group guided process wizard opens to assist in the configuration of the cluster resource. Microsoft failover clusters allows you to use any text string for the name of a resource. By default, Oracle Fail Safe uses the instance ID for the database. You can change the name to something more meaningful if desired. For example, the cluster resource name is changed to "Test Database" here.
On this page, select the cluster group that will own the database. This group should own the disks used by the database. If Oracle Fail Safe finds that any of the disks are owned by a different group, then it asks you if you want to move those disks to the selected group.
If there are more than two nodes in the cluster, then it is necessary to determine which nodes could possibly host the database. Select the desired nodes from the Available list and move them to the Selected list. If any of the resources currently residing in the group exclude one of the nodes as a possible owner, then that node is shown in the Unavailable list. Also, the nodes that are not currently online is shown in the Unavailable list.
If the cluster group has multiple network virtual addresses and it currently does not have any Oracle network TNS listeners configured, then you must select the addresses the new network listener should use for incoming database connections. Select the desired virtual addresses from the Available list and move them to the Selected list.
The Database Parameters file field is retrieved automatically. Enter the file name for the database parameters file (
pfile). For most applications it is best to store the pfile on a shared disk in the group rather than on a node local disk. However, in situations where some nodes may not have the same resources available (such as memory or CPUs), it may be helpful to use a different pfile for each node in the cluster so that the database can be started using parameters that are appropriate for each particular node. However, when using local files, the pfile must have the same path and file name, that is, each node must use the exact file name that is entered on this page.
On this page, if the operating system authentication is not enabled, then the database is configured to use either operating system authentication or password authentication through the SYS database account.
If an Oracle Home User is configured, then Oracle Fail Safe displays an additional set of password fields for the Oracle Home User. Ensure that you provide the Oracle Home User password too.
Click Finish to begin the process of configuring the database so that it may be accessed as a cluster resource.
Clicking Finish opens the Adding resource to group progress window.