Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Thanks tor Howord Rogers
Hi Charlie
Did you have two network cards in your PC/Labtop? It's because according to note 184821.1 we need 2 IPs, one public and the other for internal network between two nodes. If that is the case I think we need two NICs right?
Also how did you install the second Linux, as virtual disk from the first Linux installation or you installed a new fresh Linux from physical disk?
I am reading James Morle's paper but it seems like he only had one Oracle sofwtare installed (unlike a normal RAC installation where both nodes have Oracle sofwtare). Instead he shared them using NFS. Using his way the installation is not that realistic, RCP is not used to transfer the software from one node to another, and we dont have to follow any of the steps in note 184821.1
Cheers
charlie cs wrote:
> It is 9.2.0.1.0
>
> 1) install vmware 3.2 on linux (red-hat 7.2)
> 2) install another two copies of linuxs (7.2, red-hat) as vetural machine A
> and B
> 3) download a new kernel, (mine 2.4.17), and rebuild it to enable LVM, and
> softdog support. Consult metalink Note:166830.1(RAC on linux single node)
> and 184821.1
> 4) install a plain disk on vatural machine A
> consult http://www.vmware.com/support/reference/win/plaindisk_win.html
> it is talking about windows and vmware 2.0, but for VMware 3.0
> and Linux 7.2, it is the exact the same steps
> 5) on vetural machine B, install the plain disk using the same files
> 6) edit linux.cfg of vetural machine A and B, add disk.locking="FALSE"
> if one of the machine is locking the disk, installation will proceed, you
> will not know the installation failed, but it will not work. If you find
> some files like READWRITE.lock along with your vetural machine files, one
> machine is locking the plain disk, fix the problem so that no node is
> locking the shared disk
> 7) start both vetural machine, with one connected with cd-rom, other one not
> connected, otherwise you will not be able to take out the cd during your
> installation
> 8) create two logical volumes, and then two raw device
> like /dev/raw/quoram_disk, /dev/raw/ora_CmdFile
> consult metalink Note:166830.1 and 184821.1 again.
> 9)on both machine, as root,
> $vgchange -a y oracle_vg (I created the volume group as oracle_vg)
> $lvscan
> to make sure the logical volume is active
> 10)install oracle from vetural machine A,
> consult note 184821.1 on metalink
> install cluster manager first
> follow those steps for 9.2+, start oracm and watchdog and then install
> oracle software
> 11) TRICK:
> the installation will process without error messages, but the oracle
> copy on vetural machine B is not complete, and not usable. Reboot vetural
> machine B with cdrom connected, without starting oracm and watchdog, install
> oracle software as you will do for a non-rac oracle installation, choose the
> same options as you did before, make all of them reinstall, oracle will
> finish the installation and relink them for you.
> 12) make your oracle rac-ready,
> $cd $oracle_home/redms/lib
> $make -f ins_rdbms.mk rac_on
> $make -f ins_rdbms.mk ioracle
> 13) now you are ready to create your database.
> Hope it helps. And hope somebody can repeat my procedure, and write a more
> complete and accurate step-by-step instructions.
>
> Good luck
>
>
Received on Sun Feb 16 2003 - 13:39:53 CST
![]() |
![]() |