Asm Disk Üstüne Oracle Veritabanı Kurulumu

1.AMAÇ VE KAPSAM

Asm disk alanı olusturup, ustunde veritabanını olusturmak.

2.UYGULAMA

2.1. Asm kurulumu ve yönetimi için 3 tane rpm gerekiyor , bu rpmleri oracle’in sayfasindan temin edebilirsiniz.

[root@oracle ~]# rpm -ivh Desktop/oracleasm-support-2.1.7-1.el5.i386.rpm

warning: Desktop/oracleasm-support-2.1.7-1.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159

Preparing… ########################################### [100%]

1:oracleasm-support ########################################### [100%]

[root@oracle ~]# rpm -ivh Desktop/oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm

warning: Desktop/oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159

Preparing… ########################################### [100%]

1:oracleasm-2.6.18-164.el########################################### [100%]

[root@oracle ~]# rpm -ivh Desktop/oracleasmlib-2.0.4-1.el5.i386.rpm

warning: Desktop/oracleasmlib-2.0.4-1.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159

Preparing… ########################################### [100%]

1:oracleasmlib ########################################### [100%]

2.2. Config ayarlarini yapiyoruz.

[root@oracle ~]# oracleasm configure -i

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 []: oracle

Default group to own the driver interface []: dba

Start Oracle ASM library driver on boot (y/n) [n]: y

Scan for Oracle ASM disks on boot (y/n) [y]:

Writing Oracle ASM library driver configuration: done

[root@oracle ~]# oracleasm init

Creating /dev/oracleasm mount point: /dev/oracleasm

Loading module “oracleasm”: oracleasm

Mounting ASMlib driver filesystem: /dev/oracleasm

2.3. Sisteme yeni eklemiş olduğumum sdb ve sdc disklerini 2+2 toplam 4 partionla ayiriyoruz, siz 1+1 yapip tek partiona ayirabilirsiniz.

[root@oracle ~]# fdisk /dev/sdb

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won’t be recoverable.

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

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)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n

Command action

e extended

p primary partition (1-4)

p

Partition number (1-4): 1

First cylinder (1-1305, default 1): 1

Last cylinder or +size or +sizeM or +sizeK (1-1305, default 1305): 650

Command (m for help): p

Disk /dev/sdb: 10.7 GB, 10737418240 bytes

255 heads, 63 sectors/track, 1305 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 1 650 5221093+ 83 Linux

Command (m for help): n

Command action

e extended

p primary partition (1-4)

p

Partition number (1-4): 2

First cylinder (651-1305, default 651):

Using default value 651

Last cylinder or +size or +sizeM or +sizeK (651-1305, default 1305):

Using default value 1305

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.

[root@oracle ~]# fdisk /dev/sdc

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won’t be recoverable.

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

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)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n

Command action

e extended

p primary partition (1-4)

p

Partition number (1-4): 1

First cylinder (1-1305, default 1):

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-1305, default 1305): 650

Command (m for help): n

Command action

e extended

p primary partition (1-4)

p

Partition number (1-4): 2

First cylinder (651-1305, default 651):

Using default value 651

Last cylinder or +size or +sizeM or +sizeK (651-1305, default 1305):

Using default value 1305

Command (m for help): p

Disk /dev/sdc: 10.7 GB, 10737418240 bytes

255 heads, 63 sectors/track, 1305 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdc1 1 650 5221093+ 83 Linux

/dev/sdc2 651 1305 5261287+ 83 Linux

Command (m for help): w

The partition table has been altered!

2.4. Şimdi oluşturduğumuz bu partionlari asm ye tanitip partionlara disk isimlerini veriyoruz.

Calling ioctl() to re-read partition table.

Syncing disks.

[root@oracle ~]# /usr/sbin/oracleasm createdisk DISK1 /dev/sdb1

Writing disk header: done

Instantiating disk: done

[root@oracle ~]# /usr/sbin/oracleasm createdisk DISK2 /dev/sdb2

Writing disk header: done

Instantiating disk: done

[root@oracle ~]# /usr/sbin/oracleasm createdisk DISK3 /dev/sdc1

Writing disk header: done

Instantiating disk: done

[root@oracle ~]# /usr/sbin/oracleasm createdisk DISK4 /dev/sdc2

Writing disk header: done

Instantiating disk: done

[root@oracle ~]#

[root@oracle ~]# /usr/sbin/oracleasm scandisks

Reloading disk partitions: done

Cleaning any stale ASM disks…

Scanning system for ASM disks…

[root@oracle ~]# /usr/sbin/oracleasm listdisks

DISK1

DISK2

DISK3

DISK4

2.5. ASM disklerimiz oluştu artık DBCA yı kullanıp ASM instance yaratabilirim.

[root@oracle ~]#dbca

2.6. Root olarak bir script calıstırmamızı istiyor bunun sayesinde CSS servisleri ayarlanmiş olacak.

[root@oracle ~]# xhost +

access control disabled, clients can connect from any host

[root@oracle ~]# /u01/app/oracle/product/11.1.0/db_1/bin/localconfig add

/etc/oracle does not exist. Creating it now.

Successfully accumulated necessary OCR keys.

Creating OCR keys for user ‘root’, privgrp ‘root’..

Operation successful.

Configuration for local CSS has been initialized

Cleaning up Network socket directories

Setting up Network socket directories

Adding to inittab

Startup will be queued to init within 30 seconds.

Checking the status of new Oracle init process…

Expecting the CRS daemons to be up within 600 seconds.

Cluster Synchronization Services is active on these nodes.

oracle

Cluster Synchronization Services is active on all the nodes.

Oracle CSS service is installed and running under init(1M)

2.7. ASM instance icin bir password tanimliyoruz.

2.8. 2 tane diskgroup olusturucam, DISK1 ve DISK3 u DATA1 diskgroubuna ekliyorum, DISK2 yi ise DATA2 diskgroupna ekliyorum. DISK4 u daha sonra yapacagim bir calisma icin hiçbir gruba eklemedim.

2.9. ASM kurulumumuz bitiyor,artık veritabanı kurulumuna geçebiliriz.

2.10. ASM disk grubunu seçiyoruz.

2.11. Veritabanını daha büyük olan DATA1 üstüne kuruyorum.

2.12. DATA2 yide FRA olarak gosteriyorum.

2.13. Kurulumun geri kalan kisimlari klasik oracle kurulumu gibi olacaktır.