分享
 
 
 

Oracle Fail Safe Step-By-Step Installation and Configuration

王朝oracle·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Bookmark Fixed font Go to End

Doc ID: Note:74009.1

Subject: Oracle Fail Safe Step-By-Step Installation and Configuration

Type: BULLETIN

Status: PUBLISHED

Content Type: TEXT/PLAIN

Creation Date: 08-SEP-1999

Last Revision Date: 09-MAR-2001

PURPOSE

This paper describes the installation and configuration of

a complete Oracle Fail Safe system from the scratch - no

Oracle prodUCts are even installed. A step-by-step approach

is taken to simplify the eXPlanation. After each step its

the name of the node where the operation must be submitted.

SCOPE & APPLICATION

This paper is intended to people that will install and

configure the Oracle Fail Safe.

It assumes that the MSCS is already configured and

running.

RELATED DOCUMENTS

None

1. Install Oracle 8.0.5 on <DEFAULT_HOME> (Node 1)

2. Reboot Node 1

3. Install Oracle 8.0.5 on <DEFAULT_HOME> (Node 2)

4. Reboot Node 2

5. Create a database to be added to the cluster (using Note:68720.1)

do not configure Net8 for the newly created database. Remember

control files, redo log files and datafiles all must be created in the

shared disks. (Node 1)

6. Add an ORACLE_SID variable with its value being the SID of the

database created in Step 5. to the Oracle Hive in the Registry of both

nodes. (Node 1, Node 2)

7. Install FailSafe 2.1.3 on <DEFAULT_HOME> (Server and Manager

components). (Node 1)

8. Install FailSafe 2.1.3.1 patch on <DEFAULT_HOME> (Node 1)

9. Reboot Node 1

10. Install FailSafe 2.1.3 on <DEFAULT_HOME> (Server and Manager

components). (Node 2)

11. Install FailSafe 2.1.3.1 patch on <DEFAULT_HOME> (Node 2)

12. Reboot Node 2

13. Ping the Cluster Alias and each node's hostname(you could see all

the names in the MSCS Administrator), if all reply then proceed. If

not then ask the System Administrator to check the problem. The public

IP should come first when pinging each node!

(Node 1)

14. Ping the Cluster Alias and each node's hostname(you could see all the

names in the MSCS Administrator), if all reply with the same IPs of

step 13. then proceed. If not ask the System Administrator to check

the problem. The public IP should come first when pinging each node!

(Node 2)

15. Edit %windir%\System32\Drivers\etc\hosts and add a unique hostname

and a free IP in the list (Node 1)

16. Edit %windir%\System32\Drivers\etc\hosts and add the same hostname

and IP added in 11 (Node 2)

17. Enter Fail Safe Manager(FSM): you will be prompted for four

fields. Fill the fields username and passWord with a Windows NT

Administrator, the cluster name is the root of the tree that

appears in the MSCS Administrator, the domain name is the name

of the domain that the nodes belong (it's displayed in the logon

box of NT). (Node 1)

18. In FSM choose Verify Cluster..., if any errors are detected fix them

before proceeding.

19. In FSM Choose Add a New Group ..., when asked for a Network Name choose

Network Accessible by Clients and in the Name Field put the hostname

written in the hosts file of steps 15. and 16. . You should see the

IP field being automatically filled (with the IP specified in steps

15. and 16.

, all other wizard steps are self explained. (Node 1)

20. Choose Verify Group ... in FSM to assure that the group was

created ok.

21. Copy the password file and init.ora (if it is in the private

disks) of the databases to be added to the cluster to the same path

in the other node. (Node 1, Node 2)

22. Set all Net listeners to Manual Startup. Fail Safe will start the

Listener automatically on failover. (Node 1)

23. In the FSM choose Verify Standalone Database... if everything is ok

proceed to 24., if not fix the problems detected.

24. In the FSM choose Add a Standalone Database... to the previously

created group. Be sure that no Listeners are started up when doing so.

(Node 1)

25. Make a Move to Other Node... Operation to test the configuration

(rigth-click the DB in the tree of FSM and choose that option).

(Node 1)

26. Restore the DB to the original Node 1 doing another Move to Other

Node... operation (Node 1)

.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
2023年上半年GDP全球前十五强
 百态   2023-10-24
美众议院议长启动对拜登的弹劾调查
 百态   2023-09-13
上海、济南、武汉等多地出现不明坠落物
 探索   2023-09-06
印度或要将国名改为“巴拉特”
 百态   2023-09-06
男子为女友送行,买票不登机被捕
 百态   2023-08-20
手机地震预警功能怎么开?
 干货   2023-08-06
女子4年卖2套房花700多万做美容:不但没变美脸,面部还出现变形
 百态   2023-08-04
住户一楼被水淹 还冲来8头猪
 百态   2023-07-31
女子体内爬出大量瓜子状活虫
 百态   2023-07-25
地球连续35年收到神秘规律性信号,网友:不要回答!
 探索   2023-07-21
全球镓价格本周大涨27%
 探索   2023-07-09
钱都流向了那些不缺钱的人,苦都留给了能吃苦的人
 探索   2023-07-02
倩女手游刀客魅者强控制(强混乱强眩晕强睡眠)和对应控制抗性的关系
 百态   2020-08-20
美国5月9日最新疫情:美国确诊人数突破131万
 百态   2020-05-09
荷兰政府宣布将集体辞职
 干货   2020-04-30
倩女幽魂手游师徒任务情义春秋猜成语答案逍遥观:鹏程万里
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案神机营:射石饮羽
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案昆仑山:拔刀相助
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案天工阁:鬼斧神工
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案丝路古道:单枪匹马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:与虎谋皮
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:李代桃僵
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:指鹿为马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:小鸟依人
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:千金买邻
 干货   2019-11-12
 
推荐阅读
 
 
 
>>返回首頁<<
 
靜靜地坐在廢墟上,四周的荒凉一望無際,忽然覺得,淒涼也很美
© 2005- 王朝網路 版權所有