Friday , July 21 2017
Home / Oracle DBA / ASM DISK Creations

ASM DISK Creations

ASM DISK Creations

  • Configure ASM Driver
  • Create ASM DISKS
  • CREATE ASM DISK Groups – under during GI Install

Configure ASM Driver

—Make sure ASM packages has to install

[root@node2 u01]# rpm -qa|grep oracle
oracleasm-support-2.1.3-1.el5
oracleasm-2.6.18-194.el5debug-2.0.5-1.el5
oracleasm-2.6.18-194.el5xen-2.0.5-1.el5
oracle asm-2.6.18-194.el5-2.0.5-1.el5
oracle-validated-1.0.0-22.el5
oracle-logos-4.9.17-6
oracleasm-2.6.18-194.el5PAE-2.0.5-1.el5

[root@node1 u01]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets (‘[]’). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: grid
Default group to own the driver interface []: asmdba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done

Initializing the Oracle ASMLib driver:                     [ OK ]

Scanning the system for Oracle ASMLib disks:               [ OK ]

—-Then SAN Storage has to point NODE1 and NODE2 Machines.

[root@node2 u01]# fdisk -l

 Disk /dev/sda: 42.9 GB, 42949672960 bytes –This is space to point to NODE1

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot     Start         End     Blocks   Id System

/dev/sda1   *           1       1275   10241406   83 Linux

/dev/sda2           1276       1657     3068415   82 Linux swap / Solaris

/dev/sda3            1658       5221   28627830   83 Linux

 [root@node2 u01]# fdisk /dev/sda

The number of cylinders for this disk is set to 5221.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups 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)

Command (m for help): m

Command action


a&nbsp;&nbsp; toggle a bootable flag

b&nbsp;&nbsp; edit bsd disklabel

c&nbsp;&nbsp; toggle the dos compatibility flag

d&nbsp;&nbsp; delete a partition

l&nbsp;&nbsp; list known partition types

m&nbsp;&nbsp; print this menu

n&nbsp;&nbsp; add a new partition

o&nbsp;&nbsp; create a new empty DOS partition table

p&nbsp;&nbsp; print the partition table

q&nbsp;&nbsp; quit without saving changes

s &nbsp;create a new empty Sun disklabel

t&nbsp;&nbsp; change a partition's system id

u&nbsp;&nbsp; change display/entry units

v&nbsp;&nbsp; verify the partition table

w&nbsp;&nbsp; write table to disk and exit

x&nbsp;&nbsp; extra functionality (experts only)

Command (m for help): &lt;strong&gt;n&lt;/strong&gt;

Command action

e&nbsp;&nbsp; extended

p&nbsp;&nbsp; primary partition (1-4)

We have to create disks in physical memory are ( 1 – 4 )

  • Primary partition – 1,2,3
  • Logical partition (extended) e – 4
P – OCR +1g
P – OCR +1g
P- OCR +1g
Ext –DATA +12g
Ext – FRA +8g
Read More:
Oracle RAC Architecture
Linux Installation
Install Database Software Only

Comments

comments

Check Also

ORA-01102: cannot mount database in EXCLUSIVE mode

ORA-01102 ORA-09968 Error While Starting Oracle Database: Comments comments

Leave a Reply

Your email address will not be published. Required fields are marked *