How to add a shared disk to a VM to support ORACLE 10G RAC

Adding a shared disk to a VM supports ORACLE 10g rac. Because the original ASM shared disk capacity is small, it is impossible to mount the archive log and backup files. so I decided to add a disk. 1. Add a virtual disk to node 1 and place it in the original shared directory named ASM4. Select SCSI. Note that the disk is placed behind another disk on SCSI bus 1, otherwise, it is easy to change the drive letter mode = independent-> Persistent www.2cto.com 2 to close the VM file, and then use UEDIT to open Red Hat Enterprise Linux 4.vmx at the end of the file scsi1: 5. present = "TRUE" scsi1: 5. fileName = "F: \ sharkdisk \ asm4.vmdk" scsi1: 5. mode = "independent-persistent", you can see that ASM4 is successfully added to the original shared disk. locking = "fa Lse "diskLib. dataCacheMaxSize = "0" diskLib. dataCacheMaxReadAheadSize = "0" diskLib. dataCacheMinReadAheadSize = "0" diskLib. dataCachePageSize = "4096" diskLib. maxUnsyncedWrites = "0" -- scsi1.sharedBus = "VIRTUAL" is the shared bus added by others. I did not add this line! Scsi1: 0. deviceType = "disk" scsi1: 1. deviceType = "disk" scsi1: 2. deviceType = "disk" scsi1: 3. deviceType = "disk" scsi1: 4. deviceType = "disk" scsi1: 5. deviceType = "disk" 3 Node 2 add an existing virtual disk. On the editing machine, select disk, select an existing disk and locate ASM4 in the shared directory. Set SCSI and independent = Persistent4 to close the VM file. Then use UEDIT to open Red Hat Enterprise Linux 4.vmx and add scsi1: 5. deviceType = "disk" 5 Start Node 1 switch to the new fdisk under the ROOT user
[Root @ node1 ~] # Fdisk-lDisk/dev/sdh: 8589 MB, 8589934592 bytes255 heads, 63 sectors/track, 1044 cylindersUnits = cylinders of 16065*512 = 8225280 bytes www.2cto.com Disk/dev/sdh doesn't contain a valid partition table [root @ node1 ~] # Fdisk/dev/sdh [root @ node1 ~] # Fdisk/dev/sdhDevice contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabelBuilding a new DOS disklabel. changes will remain in memory only, until you decide to write them. after that, of course, the previuscontent won't be recoverable. the number of cylinders for this disk is set to 1044. there is nothing wrong with that, but this is larger than 1024, and cocould in certain setu Ps cause problems with: 1) software that runs at boot time (e.g ., old versions of LILO) 2) booting and partitioning software from other OSs (e.g ., dos fdisk, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w (rite) www.2cto.com Command (m for help ): n -- create partition Command action e extended p primary Partition (1-4) p -- primary partition Partition number (1-4): 1 -- partition number 1 First cylinder (1-10 44, default 1): 1 -- Last cylinder or + size or + sizeM or + sizeK (1-1044, default 1044) starting from cylindrical 1 ): 1044 -- to The last cylindrical Command (m for help): w -- save The partition table has been altered! Calling ioctl () to re-read partition table. Syncing disks. [root @ node1 ~] # [Root @ node1 ~] #/Etc/init. d/oracleasm createdisk VOL4/dev/sdh1Marking disk "VOL4" as an ASM disk: [OK] [root @ node1 ~] #/Etc/init. d/oracleasm listdisksVOL1VOL2VOL3VOL4 www.2cto.com 6 startup Node 2 partition found, and the ASM disk has been found [root @ node2 ~] # Fdisk-lDisk/dev/sdh: 8589 MB, 8589934592 bytes255 heads, 63 sectors/track, 1044 cylindersUnits = cylinders of 16065*512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/sdh1 1 1044 8385898 + 83 Linux [root @ node2 ~] #/Etc/init. d/oracleasm listdisksVOL1VOL2VOL3VOL4