RHEL5, ASM question and rules.d

Hello

We're having trouble setting up ASM 11 g on RHEL5. The oracle account is able to see the disks.
When you run Setup from the location of the grid software and selecting "install and set up the infrastructure of the network for a stand-alone server, the drives are not listed as candidate disks. the entries on this screen are: QDATA group name, external redundancy, the disk and to add disks, there is nothing listed. I guess that the disk permissions are correct, but I was wondering if maybe they aren't. I read that it should be entered in the files etc/udev/rules.d/50-udev.rules, but am confused about which applies in this case and if so, what would the Scriptures EMC disk. We install the user oracle DBA goup.

Oracle@cwb02efnora04:/U01/app/Oracle > oracleasm listdisks
QDATA1
QDATA2
QDATA3
QDATA4
QDATA5
QFLASH1
QFLASH2

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

#######################################
# Persistent block device stuff - start
#######################################
links persistent disk #: / dev/disk / {by uuid, by id, by road, by label}
schema of # based on "Device names persistent Linux", 2004, Hannes Reinecke < [email protected] >

ACTION! = 'Add', GOTO = "persistent_end."

KERNEL == "dm-[0-9] ' * ', GOTO = 'persistent_end'"

KERNEL == "nst [0-9] ' * ', IMPORT {parent} ==" ID_ * ' "
"KERNEL ==" nst [0-9] "*", SUBSYSTEM is "scsi_tape", ENV {ID_SERIAL} is "", IMPORT {program} = 'scsi_id u g - x s %p d $tempnode'
"KERNEL ==" nst [0-9] "*", SUBSYSTEM is "scsi_tape", ENV {ID_SERIAL} is "", IMPORT {program} = 'scsi_id u g - x - a s %p d $tempnode'
KERNEL == "nst [0-9]" * ", SUBSYSTEM is"scsi_tape", ENV {ID_SERIAL} is"? "*", SYMLINK += "Ribbon/by-id / $env {ID_BUS} - {ID_SERIAL} $env"-nst ""

8 type units # are 'Medium Changers '.
KERNEL == "sg *", IMPORT {parent} == "ID_."
"KERNEL ==" sg * "SUBSYSTEM is"scsi_generic", SYSFS {type} is '8', ENV {ID_SERIAL} is" ", IMPORT {program} =" scsi_id-g u - x %p d $tempnode s.
"KERNEL ==" sg * "SUBSYSTEM is"scsi_generic", SYSFS {type} is '8', ENV {ID_SERIAL} is" ", IMPORT {program} =" scsi_id-g-u - x - a s %p d $tempnode.
KERNEL == "sg *" subsystem is "scsi_generic", SYSFS {type} is '8', ENV {ID_SERIAL} is "?" "*", SYMBOLIC link += "Ribbon/by-id / $env {ID_BUS} - $env {ID_SERIAL} '"

Subsystem "!" = 'block', GOTO = "persistent_end."

# ignore rules for inappropriate block devices
KERNEL == "ram * |" loop * | FD * | * nbd | "gnbd * ', GOTO ="persistent_end. "

# never access removable ide devices, the drivers are originally event loops on open()
BUS "ide", PILOT of ==! = 'ide-cdrom", SYSFS {removable} is '1', GOTO ="persistent_end. "
BUS == "ide" KERNEL == "hd * [0-9]", SYSFS {.. / removable} == '1', GOTO = "persistent_end."

# by id (serial number of the equipment)
KERNEL == "hd * [!]" 0-9]', IMPORT {program} = "" / lib/udev/ata_id - export $tempnode ""
KERNEL == "hd * [!]" 0-9]", ENV {ID_SERIAL} =="? " «* ", SYMBOLIC link +=" disk/by-id/ata - $env {ID_MODEL} _ {ID_SERIAL} $env"
KERNEL == "hd * [0-9]", IMPORT {parent} == "ID_ *", SYMBOLIC link += "disk/by-id/ata-$env{ID_MODEL}_$env{ID_SERIAL}-part%n."

KERNEL == "sd * [!]" 0-9] | "sr *", SYSFS {ieee1394_id} == "" * ", ENV {ID_SERIAL} ="$sysfs {ieee1394_id}", ENV {ID_BUS} ="IEEE 1394""
KERNEL == "sd * [!]" 0-9] | "" sr * ", ENV {ID_SERIAL} ==" ", IMPORT {program} =" / lib/udev/usb_id - x.
KERNEL == "sd * [!]" 0-9] | «"sr *", ENV {ID_SERIAL} == "", IMPORT {program} = "/ lib/udev/scsi_id - g - s %p d $tempnode x»
KERNEL == "sd * [!]" 0-9] | "" sr * ", ENV {ID_SERIAL} ==" ", IMPORT {program} =" / lib/udev/scsi_id - g - x - a s %p d $tempnode.
KERNEL == "dasd * [!]" 0-9]', IMPORT {program} = "" / lib/udev/dasd_id - export $tempnode ""
KERNEL == "nst [0-9] * |" St * | SD * [! 0-9] | SR * | DASD * [! 0-9] | CCISS? c", ENV {ID_SERIAL} =="? " "*", SYMBOLIC link += "disk/by-id / $env {ID_BUS}-$env {ID_SERIAL} '"
KERNEL == "nst [0-9] * |" St * | SD * [! 0-9] | SR * | DASD * [! 0-9] | CCISS? c", ENV {ID_UID} =="? " "*", SYMBOLIC link += "disk/by-id / $env {ID_BUS}-$env {ID_UID} '"

# to import parent information sheet music
KERNEL == "sd * [0-9] |" "dasd * [0-9]", IMPORT {parent} == "ID_."
KERNEL is "cciss? d c [0-9] [0-9]", ENV {ID_SERIAL}! =" ? ' * ', IMPORT {program} = "scsi_id g - x s %p d $tempnode", ENV {ID_BUS} = "cciss"
KERNEL is "cciss? d c [0-9] [0-9]", ENV {ID_SERIAL}! =" ? ' * ', IMPORT {program} = "scsi_id g - x - a s %p d $tempnode", ENV {ID_BUS} = "cciss"
KERNEL == "sd * [0-9] |" DASD * [0-9] | "cciss * p [0-9]", ENV {ID_SERIAL} == "?" "*", SYMBOLIC link += "disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n."
KERNEL == "sd * [0-9] |" DASD * [0-9] | "cciss * p [0-9]", ENV {ID_UID} == "?" "*", SYMBOLIC link += "disk/by-id/$env{ID_BUS}-$env{ID_UID}-part%n."

by-path # (shorter physical path)
KERNEL == "* [!]" 0-9] | "sr *", ENV {ID_TYPE} == "?" "* ', IMPORT {program} =" "/ lib/udev/path_id %p", SYMBOLIC link += "disk/by-path / $env {ID_PATH} '"
KERNEL == "m *", IMPORT {program} = "path_id %p", SYMBOLIC link += "Ribbon/by-path / $env {ID_PATH}".
KERNEL == "sr * |" * st', GOTO = "persistent_end."
KERNEL == "* [0-9]", IMPORT {parent} == "ID_ * '"
KERNEL == "* [0-9]", ENV {ID_PATH} == "? "*", SYMBOLIC link += "disk/by-path/$env{ID_PATH}-part%n."

# by-label/by-uuid (file system properties)
KERNEL == "* [!]" 0-9]", SYSFS {removable} is '1', GOTO ="persistent_end. "
IMPORT {program} = "" / lib/udev/identifiant_volume - export $tempnode ""
ENV {ID_FS_UUID} == "?" "*", SYMBOLIC link += "disk/by-uuid / $env {ID_FS_UUID}".
ENV {ID_FS_LABEL_SAFE} == "?" "*", SYMBOLIC link += "disk/by-label / $env {ID_FS_LABEL_SAFE}".

# BIOS Enhanced Disk Device
KERNEL == "* [!]" 0-9]', IMPORT {program} = "" / lib/udev/edd_id - export $tempnode ""
KERNEL == "* [!]" 0-9]", ENV {ID_EDD} =="? " "*", SYMBOLIC link += "disk/by-id/ESD - $env {ID_EDD}".
KERNEL == "* [0-9]", ENV {ID_EDD} == "? "*", SYMBOLIC link += "disk/by-id/edd-$env{ID_EDD}-part%n."

LABEL = "persistent_end".

#####################################
# Tricks of persistent block - end device
#####################################

Published by: user632322 on January 26, 2010 13:36

Now you can return to the pop-up screen and click OK, then it will run a few clusters check orders.
At this point, you should be able run crs_stat t of the $ORA_CRS_HOME/bin and see the gsd, ons and resources vip in the crs stack. You now have a stack of cluster. Now, install the binary files of DB and make install software "only".
The changes to the standard .bash_profile, or what ever bomb you they use for the oracle unix user name so that the oracle_home and ora_crs_home paths are known.

Now ready for the icing on the cake using dbca. DBCA is the simplest method, but I set myself some listeners, asm and data bases from scratch. When you run dbca you will be asked if a listener does not already exist, and that you will also be asked to implement asm disk groups according to the choices made. After choosing the DSO of installation you will be presented in step 3 of 5 ASM instance create. Click on the button "settings of ASM...". ». The next screen popup will give you the choice of 3 parameters. To the right of the parameter asm_diskstring in the choice of value column the access path to the DSO from your drive, in my case, I'm going home "/ raw/asm. After you click OK on screen 3 5 a pop up should see the DBCA will now create and start the ASM... then click OK.
.. Suite...

Then again another pop up screen and show that he "failed to retrieve network listener resources... and you want to create listeners on port 1521 "then click OK again. At this point, you should now see a screen that says something like "using the ASM disks groups page, you can view and manage existing groups... etc, then click on"Create New"in the lower left corner." At this point you should now be presented with a screen to enter a disk group, enter its name, click the external radio button, click the option button to show the candidates. In my case for my group of asm Archives, I chose ARCH, external redundancy, candidates show and click on the box to the left empty the/raw/asm/arch.
Repeat the same steps for your other starts from the DSO.

Then you can move to the creation of the database where you will be prompted to use ASM groups you just created. Remember that this is asm so a disk group name has a plus '+' in front of it. If you are having problems just choose a disk group later edit your database once it is up and running.

How it works for you?

-JR jr.

Tags: Database

RHEL5, ASM question and rules.d

Similar Questions

Maybe you are looking for