Oracle Fail Safe Step-By-Step Installation and Configuration

 1<default_home> (Node 1)   
 22\. Reboot Node 1   
 33\. Install Oracle 8.0.5 on <default_home> (Node 2)   
 44\. Reboot Node 2   
 55\. Create a database to be added to the cluster (using Note:68720.1)   
 6do not configure Net8 for the newly created database. Remember   
 7control files, redo log files and datafiles all must be created in the   
 8shared disks. (Node 1)   
 96\. Add an ORACLE_SID variable with its value being the SID of the   
10database created in Step 5. to the Oracle Hive in the Registry of both   
11nodes. (Node 1, Node 2)   
127\. Install FailSafe 2.1.3 on <default_home> (Server and Manager   
13components). (Node 1)   
148\. Install FailSafe 2.1.3.1 patch on <default_home> (Node 1)   
159\. Reboot Node 1   
1610\. Install FailSafe 2.1.3 on <default_home> (Server and Manager   
17components). (Node 2)   
1811\. Install FailSafe 2.1.3.1 patch on <default_home> (Node 2)   
1912\. Reboot Node 2   
2013\. Ping the Cluster Alias and each node's hostname(you could see all   
21the names in the MSCS Administrator), if all reply then proceed. If   
22not then ask the System Administrator to check the problem. The public   
23IP should come first when pinging each node! (Node 1)   
2414\. Ping the Cluster Alias and each node's hostname(you could see all the   
25names in the MSCS Administrator), if all reply with the same IPs of   
26step 13. then proceed. If not ask the System Administrator to check   
27the problem. The public IP should come first when pinging each node!   
28(Node 2)   
2915\. Edit %windir%\System32\Drivers\etc\hosts and add a unique hostname   
30and a free IP in the list (Node 1)   
3116\. Edit %windir%\System32\Drivers\etc\hosts and add the same hostname   
32and IP added in 11 (Node 2)   
3317\. Enter Fail Safe Manager(FSM): you will be prompted for four   
34fields. Fill the fields username and password with a Windows NT   
35Administrator, the cluster name is the root of the tree that   
36appears in the MSCS Administrator, the domain name is the name   
37of the domain that the nodes belong (it's displayed in the logon   
38box of NT). (Node 1)   
3918\. In FSM choose Verify Cluster..., if any errors are detected fix them   
40before proceeding.   
4119\. In FSM Choose Add a New Group ..., when asked for a Network Name choose   
42Network Accessible by Clients and in the Name Field put the hostname   
43written in the hosts file of steps 15. and 16. . You should see the   
44IP field being automatically filled (with the IP specified in steps   
4515\. and 16. , all other wizard steps are self explained. (Node 1)   
4620\. Choose Verify Group ... in FSM to assure that the group was   
47created ok.   
4821\. Copy the password file and init.ora (if it is in the private   
49disks) of the databases to be added to the cluster to the same path   
50in the other node. (Node 1, Node 2)   
5122\. Set all Net listeners to Manual Startup. Fail Safe will start the   
52Listener automatically on failover. (Node 1)   
5323\. In the FSM choose Verify Standalone Database... if everything is ok   
54proceed to 24., if not fix the problems detected.   
5524\. In the FSM choose Add a Standalone Database... to the previously   
56created group. Be sure that no Listeners are started up when doing so.   
57(Node 1)   
5825\. Make a Move to Other Node... Operation to test the configuration   
59(rigth-click the DB in the tree of FSM and choose that option).   
60(Node 1)   
6126\. Restore the DB to the original Node 1 doing another Move to Other   
62Node... operation (Node 1)   
63.</default_home></default_home></default_home></default_home></default_home></default_home>