1. All configurations are the same as the file system . 2. Planning:
Added 8 small plates, ASM for experiment using Asmlib Drive (rhel6 no longer supports Asmlib drive), 2 methods for bare devices (Rowdevice and Udev)
Three discs using Asmlib, two using Rowdevice, two using Udev 2. Partitioning
(1) View
[Email protected] ~]# fdisk-l
disk/dev/sda:16.1 GB, 16106127360 bytes
255 heads, Sectors/track, 1958 cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
/DEV/SDA1 * 1 104391 Linux
/dev/sda2 1958 15623212+ 8e Linux LVM
Disk/dev/sdb: 1073 MB, 1073741824 bytes
255 heads, Sectors/track, cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
Disk/DEV/SDC: 1073 MB, 1073741824 bytes
255 heads, Sectors/track, cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
disk/dev/sdd:1073 MB, 1073741824 bytes
255 heads, Sectors/track, cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
disk/dev/sde:1073 MB, 1073741824 bytes
255 heads, Sectors/track, cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
disk/dev/sdf:1073 MB, 1073741824 bytes
255 heads, Sectors/track, cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
disk/dev/sdg:1073 MB, 1073741824 bytes
255 heads, Sectors/track, cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
disk/dev/sdh:2147 MB, 2147483648 bytes
255 heads, Sectors/track, 261 cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
disk/dev/sdi:1073 MB, 1073741824 bytes
255 heads, Sectors/track, cylinders
Units = Cylinders of 16065 * 8225280 bytes
Device Boot Start End Blocks Id System
(2) Fdisk/dev/sdb
Order of instruction: N--P--1--Enter--Enter---W
/DEV/SDC/DEV/SDD/DEV/SDE/DEV/SDF/DEV/SDG/DEV/SDH/DEV/SDI perform the same operation 3. Create disk groups and bare devices
[Email protected] ~]# UNAME-RM
2.6.18-308.el5 x86_64
: http://www.oracle.com/technetwork/server-storage/linux/downloads/index-088143.html
Create an ASM disk group
(1) The following is the way to create a disk group through Asmlib, creating
/etc/init.d/oracleasm Configure
/etc/init.d/oracleasm Createdisk V1/DEV/SDB1
/etc/init.d/oracleasm Createdisk V2/DEV/SDC1
/etc/init.d/oracleasm Createdisk V3/DEV/SDD1
/etc/init.d/oracleasm Scandisks
/etc/init.d/oracleasm Listdisks
(2) The following method is configured by Rowdeviece mode
Configuration file/etc/sysconfig/rawdevices
Add to:
/dev/raw/raw1/dev/sde1
/dev/raw/raw2/dev/sdf1
/dev/raw/raw3/dev/sdg1
Start the service
/etc/init.d/rawdevices start
View
[Email protected] ~]# RAW-QA
/dev/raw/raw1:bound to Major 8, minor 65
/dev/raw/raw2:bound to Major 8, minor 81
/dev/raw/raw3:bound to Major 8, minor 97
Modify Permissions
Chown oracle:oinstall/dev/raw/raw{1,2,3}
chmod 660/dev/raw/raw{1,2,3}
[Email protected] ~]# ls-l/dev/raw
Total 0
CRW-RW----1 Oracle Oinstall 162, 1 Sep 2 19:24 raw1
CRW-RW----1 Oracle Oinstall 162, 2 Sep 2 19:24 raw2
CRW-RW----1 Oracle Oinstall 162, 3 Sep 2 19:24 raw3
(3) Using Udev method
[Email protected] raw]# Vi/etc/udev/rules.d/60-raw.rules
# Enter Raw device bindings here.
#
# A example would be:
# action== "Add", kernel== "SDA", run+= "/bin/raw/dev/raw/raw1%N"
# to BIND/DEV/RAW/RAW1 TO/DEV/SDA, or
# action== "Add", env{major}== "8", env{minor}== "1", run+= "/bin/raw/dev/raw/raw5%M%M"
# to BIND/DEV/RAW/RAW5 to the device with major 8, minor 1.
action== "Add", kernel== "Sdh1", run+= "/bin/raw/dev/raw/raw4%N"
action== "Add", kernel== "Sdi1", run+= "/bin/raw/dev/raw/raw5%N"
kernel== "raw[4-5]", owner= "Oracle", group= "Oinstall", mode= "660 "
Restart Service
/sbin/start_udev
View:
[Email protected] ~]# ls-l/dev/raw
Total 0
CRW-------1 root root 162, 1 Sep 2 19:24 raw1
CRW-------1 root root 162, 2 Sep 2 19:24 raw2
CRW-------1 root root 162, 3 Sep 2 19:24 raw3
CRW-RW----1 Oracle Oinstall 162, 4 Sep 2 19:33 raw4
CRW-RW----1 Oracle Oinstall 162, 5 Sep 2 19:33 raw5
The following raw4, RAW5 for the use of Udev binding device, the advantage is that you can directly attach permissions and groups directly to the bare device, reboot does not need to modify the permissions again, but with the above Rawdevice way, you need to manually modify the permissions of the bare device.
The bare devices that can now be used by ASM disks are:
3 Disk groups V1 V2 V3
3 pieces of rawdevece configuration of the bare device
2. Udev configuration of bare device 3, start to install Oracle soft
Execute Runinstaller ( it is recommended that you do not create a new ASM disk and instance when installing the software, and then build the ASM instance when dbca the repository )
Create ASM at DBCA
Visible, all the bare devices have been identified
, OK, start selecting the required disk device, and click Next to start the installation.
4. Some problems encountered during installation first, DBCA configuring ASM instances
Solve
Please run the following batch files in the $ORACLE _home/bin directory (under root user)
Localconfig Delete
[[email protected] bin]#./localconfig Delete
/etc/init.d/init.cssd:line 519:/etc/oracle/scls_scr/localhost/root/cssrun: No
Have that file or directory
/bin/touch:cannot Touch '/ETC/ORACLE/SCLS_SCR/LOCALHOST/ROOT/NOOPROCD ': No
that file or directory
/bin/touch:cannot Touch '/etc/oracle/scls_scr/localhost/root/noclsmon ': No
that file or directory
Stopping CSSD.
Failure in CSS initialization opening OCR.
Shutdown has begun. The daemons should exit soon.
Localconfig add
[Email protected] bin]#./localconfig add
Successfully accumulated necessary OCR keys.
Creating OCR keys for user ' root ', privgrp ' root '.
Operation successful.
Configuration for local CSS have been initialized
Adding to Inittab
Startup'll is queued to init within seconds.
Checking the status of new Oracle init process ...
Expecting the CRS daemons to being up within-seconds.
CSS is active on these nodes.
localhost
CSS is active in all nodes.
Oracle CSS Service is installed and running under init (1M)
This'll help you to solve your problem
The problem is solved, and the ASM instance can start
If it cannot be performed, reboot the system. Second, when the above problem is resolved, the following ora-00600 error is reported when the ASM instance is created
Solve:
Looked it up on the Internet. Modifying the hostname will cause this problem. And friends confirmed a bit, indeed have modified the machine's hostname, the reason is clear, to begin to solve is very simple, modify the/etc/hosts file, add Hostanme can.
Other Notes:
Description of document Doc id:note:5486074.8 on Oracle's Meatlink: This error message occurs when Oracle cannot determine the hostname or network address.
Oracle resolves this bug in 10.2.0.4 and 11.1.0.6. Oracle's Metalink indicates that this error could have been caused before 10.2.0.4.
rhel5.8 Installing Oracle 10g ASM