Wheather ASM Disk need to be configured before Oracle 11gR2 Grid software

Hi All,
I have a confusion regarding ASM Disk configuration. Whether this need to be done before the grid software installation or shall we do it after grid software installation.
Kindly Advice over the same

vk82 wrote:
Hi All,
I have a confusion regarding ASM Disk configuration. Whether this need to be done before the grid software installation or shall we do it after grid software installation.
Kindly Advice over the same
ASM is going to be a storage option. The storage that would be used by the ASM instance must be available already. The installation of the GI would be on the file system of the node.
HTH
Aman....

Similar Messages

  • Oracle 11gR2 RAC Installation - ASM Disks - Need advice on configurations

    Hi Guys
    How many disks are needed for Voting, Data, Log and Failover. Each should be in a seperate group or it can be in a single group of disk. Please advice. Thanks.

    Hi Friend,
    Option 1 :
    If Oracle Clusterware is used for implementing normal redundancy. We require the following for failover purpose also.
    1. Two OCR files - 280 MB each
    2. Three Voting Disks - 280 MB each
    Total - 1.4 GB approx
    Option 2 :
    Oracle recommends that the disk used for the file system be on a RAID. When you use external redundancy the minimum requirement is One OCR and One Voting Disk with 280 MB each.
    Choices :
    1. External Redundancy - > Minimum No Of Disks (1) - > One OCR (280 MB) and One Voting Disk (280 MB) -> 580 MB
    2. Normal Redundancy - > Minimum No Of Disks (3) - > Two OCR (560 MB) and Three Voting Disk (840 MB) -> 1.4 GB
    3. High Redundancy - > Minimum No Of Disks (5) - > Three OCR (840 MB) and Five Voting Disk (1.4 GB) -> 2.3 GB
    So, Choose based on redundancy...
    Hope it helps..
    Note : Use ASM for storing above files..
    Thanks
    LaserSoft

  • Need help in configuring the Oracle app server with OC DB Server

    Hello people
    I attempted to insta;; Oracle Clinical 4.5 and I have a problem that you mayhave resolved a long time back and I need some help. This is what I have done on the installation.
    I need your help in centralizing my tnsnames.ora and sqlnet.ora files. I am an Oracle Clinical guy and not an Oracle Expert, hence the request.
    Part_1
    1. Installed Oracle 9i 9.2 database on Win2K server - W2kOCSVR
    2. Installed Oracle Clinical 4.5 and created DB on W2KOCSVR.
    3. Started up database and all is fine - tnsnames and sqlnet.ora
    4. Each of these is on a separate partition including the OS.
    Part-II
    1. Installed Oracle Appl Server 9iAs 1.0.2.2.2a on another machine OCMIDTIER. This installed Oracle iSuites home and stuff.
    2. Then I installed Oracle 9i developer suite - Oracle forms and reports.
    3. Installed Jinitiator 1.1.8.24 on the middle tier machine.
    4. Basically this is the middle tier that is a Webserver that will be linked to the Database Server in Part-I
    and lastly, I will have web clients with Jinitiator and a web browser.
    Requirement:
    I need to centralize the TNSNAMES.ora file and the SQLNET.ora file on all the machines. How do I do this?.
    I have the TNSNAMES.ora and the SQLNET.ora on DB server and it is working fine. However, I have noticed many tsnnames.ora files on the middle tier - OCMIDTIER. (I've left out the example files)
    a) E:\ORACLE\806\net80\admin\tnsnames.ora
    b) E:\ORACLE\806\net80\tnsapi\tnsnames.ora
    c) E:\ORACLE\iSuites\hs\admin\tnsnames.ora
    d) E:\ORACLE\iSuites\network\admin\tnsnames.ora
    All I need to know is which if these files do I need to integrate with the Tnsnames.ora file on the DB server - W2kOCSVR and how do I go about doing this?.
    Your help is appreciated. If I were to see a copy of your tnsnames.ora on the webserver (middle tier) and the sqlnet.ora, I will be able to get an idea of how this is done. Right now, I am using tnsnames.ora but once I learn how this ties up, I can move to names sever.
    Thanks for your help.
    Cecil

    Hi Cecil,
    I got into the same issue. I copied the content from the good tnsnames.ora to tnsnames.ora on webserver and it worked fine. I copied the details of the connect string that was working fine on dbserver. i was working on W2k server. Hope this helps
    Gonnagar

  • ASM disks in RAC need to be shared disks?

    Hi all,
    sorry for the very basic question but I'm getting a lot of confusion...
    I have clusterware installed on node1 and node2 and I'm going to create ASM instances on both nodes.
    Does the ASM disks need to be physically shared among the two nodes?
    Many thanks for help
    aldo

    ...I've brutally tried both ways and found the answer. Yes the disks need to be physically shared
    aòdp

  • Oracle 11gR2 RAC Grid installation - Configuration of ASM failed,

    Hi guys,
    Trying to install/configure Oracle 11gR2 Grid for 2 nodes RAC on Suse 10, root.sh failed with this error:
    2010-08-19 15:30:47: Querying for existing CSS voting disks
    2010-08-19 15:30:47: Performing initial configuration for cluster
    2010-08-19 15:30:48: Start of resource "ora.ctssd -init" Succeeded
    2010-08-19 15:30:48: Configuring ASM via ASMCA
    2010-08-19 15:30:48: Executing as oracle: /u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName DATA -diskList ORCL:DATA1,ORCL:DATA2 -redundancy EXTERNAL -configureLocalASM
    2010-08-19 15:30:48: Running as user oracle: /u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName DATA -diskList ORCL:DATA1,ORCL:DATA2 -redundancy EXTERNAL -configureLocalASM
    2010-08-19 15:30:48: Invoking "/u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName DATA -diskList ORCL:DATA1,ORCL:DATA2 -redundancy EXTERNAL -configureLocalASM" as user "oracle"
    2010-08-19 15:30:51: Configuration of ASM failed, see logs for details
    2010-08-19 15:30:51: Did not succssfully configure and start ASM
    2010-08-19 15:30:51: Exiting exclusive mode
    2010-08-19 15:30:51: Command return code of 1 (256) from command: /u01/app/11.2.0/grid/bin/crsctl stop resource ora.crsd -init
    2010-08-19 15:30:51: Stop of resource "ora.crsd -init" failed
    2010-08-19 15:30:51: Failed to stop CRSD
    2010-08-19 15:30:51: Command return code of 1 (256) from command: /u01/app/11.2.0/grid/bin/crsctl stop resource ora.asm -init
    2010-08-19 15:30:51: Stop of resource "ora.asm -init" failed
    2010-08-19 15:30:51: Failed to stop ASM
    2010-08-19 15:31:12: Initial cluster configuration failed. See /u01/app/11.2.0/grid/cfgtoollogs/crsconfig/rootcrs_oracle-node2.log for details
    oracle-node2:/u01/app/11.2.0/grid/cfgtoollogs/crsconfig #
    Can any one please help/assist/guide ... how to move forward?
    Thanks in advance.

    failed ... with the same error
    2010-08-19 16:52:05: Start of resource "ora.ctssd -init" Succeeded
    2010-08-19 16:52:05: Configuring ASM via ASMCA
    2010-08-19 16:52:06: Executing as oracle: /u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName DATA -diskList ORCL:DATA1,ORCL:DATA2 -redundancy EXTERNAL -configureLocalASM
    2010-08-19 16:52:06: Running as user oracle: /u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName DATA -diskList ORCL:DATA1,ORCL:DATA2 -redundancy EXTERNAL -configureLocalASM
    2010-08-19 16:52:06: Invoking "/u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName DATA -diskList ORCL:DATA1,ORCL:DATA2 -redundancy EXTERNAL -configureLocalASM" as user "oracle"
    2010-08-19 16:52:08: Configuration of ASM failed, see logs for details
    2010-08-19 16:52:08: Did not succssfully configure and start ASM
    2010-08-19 16:52:08: Exiting exclusive mode
    2010-08-19 16:52:08: Command return code of 1 (256) from command: /u01/app/11.2.0/grid/bin/crsctl stop resource ora.crsd -init
    2010-08-19 16:52:08: Stop of resource "ora.crsd -init" failed
    2010-08-19 16:52:08: Failed to stop CRSD
    2010-08-19 16:52:08: Command return code of 1 (256) from command: /u01/app/11.2.0/grid/bin/crsctl stop resource ora.asm -init
    2010-08-19 16:52:08: Stop of resource "ora.asm -init" failed
    2010-08-19 16:52:08: Failed to stop ASM
    2010-08-19 16:52:30: Initial cluster configuration failed. See /u01/app/11.2.0/grid/cfgtoollogs/crsconfig/rootcrs_oracle-node1.log for details
    oracle-node1:/u01/app/11.2.0/grid/cfgtoollogs/crsconfig #

  • DBCA Does Not Display ASM Disk Groups In 11.2.0.4

    DBCA trying to create a database with a different user oracle  than grid user. installed Grid infrastructure with user grid, and I was trying to create a database with user oracle (who’s the owner of oracle rdbms). But during this installation I wasn’t able to see any of my ASM disk. This is all under Oracle 11.2.0.4.
    what to check .. all appears ok .... at a loss at this point
    1.  asm up online   .... ok
    crs_stat -t
    Name           Type           Target    State     Host       
    ora.DATA.dg    ora....up.type ONLINE    ONLINE    sqls...r-pc
    ora.FRA.dg     ora....up.type ONLINE    ONLINE    sqls...r-pc
    ora....ER.lsnr ora....er.type ONLINE    ONLINE    sqls...r-pc
    ora.asm        ora.asm.type   ONLINE    ONLINE    sqls...r-pc
    ora.cssd       ora.cssd.type  ONLINE    ONLINE    sqls...r-pc
    ora.diskmon    ora....on.type OFFLINE   OFFLINE              
    ora.evmd       ora.evm.type   ONLINE    ONLINE    sqls...r-pc
    ora.ons        ora.ons.type   OFFLINE   OFFLINE              
    [grid@sqlservrer-PC ~]$
    2.
    2. Check your oracle binary mount point (option nosuid disable)  OK
    $ cat /etc/fstab
    UUID=f7fcc326-7c70-43ac-ba86-fe0805e1c57f /boot                   ext4    defaults        1 2
    /dev/mapper/VolGroup-loradata /oradata                ext4    defaults        1 2
    /dev/mapper/VolGroup-lorainist /orainst               ext4    defaults        1 2
    UUID=39c84d4c-6be8-4d4c-8d27-5762d2d1f7df swap                    swap    defaults        0 0
    tmpfs   
    3. ids  ok
    proc                   proc    defaults        0 0
    [grid@sqlservrer-PC ~]$ id oracle
    uid=500(oracle) gid=501(oinstall) groups=501(oinstall),500(dba),503(asmadmin),504(asmdba),505(asmoper)
    rid@sqlservrer-PC ~]$ id grid
    uid=501(grid) gid=501(oinstall) groups=501(oinstall),500(dba),503(asmadmin),504(asmdba),505(asmoper)
    4.
    4. Check  if file permissions in <Grid_home>/bin/oracle executable are set properly, it should be 6751.ok
    $ ls -l $ORACLE_HOME/bin/oracle
    -rwsr-s–x 1 grid oinstall 200678430 Jun 16 12:44 /app/11.2.0/grid/bin/oracle
    5.  ile or directory
    [grid@sqlservrer-PC ~]$ ls -alt $ORACLE_HOME/bin/oracle
    -rwsr-s--x 1 grid oinstall 209914513 Sep 17 20:02 /ora
    6. Check asm disk permissions, with two users it should be : grid — asmadmin
    $ ls -ltr /dev/oracleasm/disks/
    6.
    [grid@sqlservrer-PC ~]$ ls -altR /dev/oracleasm/disks
    /dev/oracleasm/disks:
    total 0
    brw-rw---- 1 grid asmadmin 8, 5 Sep 19 14:48 DATA1
    brw-rw---- 1 grid asmadmin 8, 6 Sep 19 14:48 FRA1
    brw-rw---- 1 grid asmadmin 8, 8 Sep 19 12:43 FRA2
    brw-rw---- 1 grid asmadmin 8, 7 Sep 19 12:42 DATA2
    drwxr-xr-x 1 root root        0 Sep 19 10:11 .
    drwxr-xr-x 4 root root        0 Sep 19 10:11 ..
    [grid@sqlservrer-PC ~]$
    5.

    Checked Metalink  apparently here is the answer.  There should be nothing wrong if you follow the above four(4)
    procedures and the output is good. Problem is when you click on ASM, click on OMF, then you have to click
    on the open pane several times before the window with Disk Groups appears.  Took 4 secs for it to appear.
    It will not be immediate.

  • ORA-15020: discovered duplicate ASM disk

    Hello.
    I am installing Oracle GI and Rdbms 11.2.0.3+, and when the installer is creating the diskgroup fail with the error ORA-15020: discovered duplicate ASM disk.
    INFO: Read: Configuring ASM failed with the following message:
    INFO: Read: One or more disk group(s) creation failed as below:
    INFO: Read: Disk Group DATA1 creation failed with the following message:
    INFO: Read: ORA-15018: diskgroup cannot be created
    INFO: Read: ORA-15020: discovered duplicate ASM disk "DATA1_0004"
    INFO: Read:
    INFO: Read:
    INFO: Completed Plugin named: Automatic Storage Management Configuration Assistant
    I have permission with all the disk:
    crw-rw---- 1 oracle dba 118, 30 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d10s6
    crw-rw---- 1 oracle dba 118, 22 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d11s6
    crw-rw---- 1 oracle dba 118, 14 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d12s6
    crw-rw---- 1 oracle dba 118, 6 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d13s6
    crw-rw---- 1 oracle dba 118, 38 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d14s6
    crw-rw---- 1 oracle dba 118, 110 Mar 6 10:49 /dev/rdsk/c1t50001FE1500B89E8d1s6
    crw-rw---- 1 oracle dba 118, 102 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d2s6
    crw-rw---- 1 oracle dba 118, 94 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d3s6
    crw-rw---- 1 oracle dba 118, 86 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d4s6
    crw-rw---- 1 oracle dba 118, 78 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d5s6
    crw-rw---- 1 oracle dba 118, 70 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d6s6
    crw-rw---- 1 oracle dba 118, 62 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d7s6
    crw-rw---- 1 oracle dba 118, 54 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d8s6
    crw-rw---- 1 oracle dba 118, 46 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d9s6
    crw-rw---- 1 oracle dba 118, 150 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd10s6
    crw-rw---- 1 oracle dba 118, 142 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd11s6
    crw-rw---- 1 oracle dba 118, 134 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd12s6
    crw-rw---- 1 oracle dba 118, 126 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd13s6
    crw-rw---- 1 oracle dba 118, 118 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd14s6
    crw-rw---- 1 oracle dba 118, 222 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd1s6
    crw-rw---- 1 oracle dba 118, 214 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd2s6
    crw-rw---- 1 oracle dba 118, 206 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd3s6
    crw-rw---- 1 oracle dba 118, 198 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd4s6
    crw-rw---- 1 oracle dba 118, 190 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd5s6
    crw-rw---- 1 oracle dba 118, 182 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd6s6
    crw-rw---- 1 oracle dba 118, 174 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd7s6
    crw-rw---- 1 oracle dba 118, 166 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd8s6
    crw-rw---- 1 oracle dba 118, 158 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd9s6
    All the partition start with the cylinder 1.
    Do you know the workaround?
    I have a open sr severity 2, but they are working too slow.
    Regards,
    Milton

    Hello Levi.
    I set the variables:
    ORACLE_HOME=/oracluster/product/11.2/clusterware
    ORACLE_SID=+ASM1
    PATH=/usr/bin:/usr/ccs/bin:/usr/ccs/bin:/sbin:/usr/sbin:/oracluster/product/11.2/clusterware/bin:/oracluster/product/11.2/clusterware/OPatch:/oracluster/product/11.2/clusterware/opmn/bin:/opt/xpdf-3.02pl1-solaris:/usr/ucb:
    NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
    ORACLE_BASE=/orasoft/product
    SSH_AUTH_SOCK=/tmp/ssh-PThz1424/agent.1424
    EDITOR=vi
    LOGNAME=oracle
    MAIL=/var/mail//oracle
    PS1=sc-prodbd0-1>(oracle):$PWD>
    LDR_CNTRL=NOKRTL
    USER=oracle
    ORACLE_HOSTNAME=sc-prodBD0-1
    SHELL=/bin/ksh
    ORACLE_TERM=vt220
    HOME=/orasoft
    LD_LIBRARY_PATH=/oracluster/product/11.2/clusterware/lib:/usr/local/lib:
    TERM=vt220

  • OUI will not detect ASM disks on EqualLogic PS6100

    RHEL 5.5 w/ ASMLIB
    Oracle 11g w/ Dell EqualLogic PS6100 iSCSI SAN
    We've created the ASM disks and can see them before starting the OUI...
    [root@dr-dbnode2 logs]# kpartx -l /dev/mapper/eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3
    eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3p1 : 0 585954747 /dev/mapper/eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3 63
    [root@dr-dbnode2 logs]# kpartx -l /dev/mapper/eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2
    eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2p1 : 0 585954747 /dev/mapper/eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2 63
    [root@dr-dbnode2 logs]# kpartx -l /dev/mapper/eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1
    eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1p1 : 0 585954747 /dev/mapper/eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1 63
    [root@dr-dbnode2 etc]# oracleasm listdisks
    ASMDATA1
    ASMDATA2
    ASMDATA3
    [root@dr-dbnode2 etc]# oracleasm querydisk -v -d -p ASMDATA1
    Disk "ASMDATA1" is a valid ASM disk on device /dev/dm-2[253,2]
    /dev/mapper/eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1p1: LABEL="ASMDATA1" TYPE="oracleasm"
    /dev/sdj1: LABEL="ASMDATA1" TYPE="oracleasm"
    [root@dr-dbnode2 etc]# oracleasm querydisk -v -d -p ASMDATA2
    Disk "ASMDATA2" is a valid ASM disk on device /dev/dm-8[253,8]
    /dev/mapper/eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2p1: LABEL="ASMDATA2" TYPE="oracleasm"
    /dev/sdf1: LABEL="ASMDATA2" TYPE="oracleasm"
    [root@dr-dbnode2 etc]# oracleasm querydisk -v -d -p ASMDATA3
    Disk "ASMDATA3" is a valid ASM disk on device /dev/dm-4[253,4]
    /dev/mapper/eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3p1: LABEL="ASMDATA3" TYPE="oracleasm"
    /dev/sdg1: LABEL="ASMDATA3" TYPE="oracleasm"
    [grid@dr-dbnode2 ext]$ kfod asm_diskstring='/dev/oracleasm/disks/*' nohdr=true verbose=true disks=all status=true op=disks
    286110 CANDIDATE /dev/oracleasm/disks/ASMDATA1 grid asmadmin
    286110 CANDIDATE /dev/oracleasm/disks/ASMDATA2 grid asmadmin
    286110 CANDIDATE /dev/oracleasm/disks/ASMDATA3 grid asmadmin
    When we run the OUI we get to the 'Add Disks' screen and there are no disks listed at all...
    So we tried to run with a -silent install and -force with the disks in our rsp file and the action log shows the following...
    [root@dr-dbnode2 logs]# cat installActions2012-01-12_05-06-51PM.log
    INFO: Waiting for completion of background operations
    INFO: Completed background operations
    INFO: Executing action at state CreateASMDiskGroup
    INFO: Completed executing action at state <CreateASMDiskGroup>
    INFO: Waiting for completion of background operations
    INFO: Completed background operations
    INFO: Moved to state <CreateASMDiskGroup>
    INFO: Waiting for completion of background operations
    INFO: Completed background operations
    INFO: Validating state <CreateASMDiskGroup>
    INFO: inventory location is/opt/oracle/app/oraInventory
    INFO: inventory location is/opt/oracle/app/oraInventory
    INFO: inventory location is/opt/oracle/app/oraInventory
    INFO: Is CRS Installed false
    INFO: while getting CSS versionjava.lang.Exception: Unable to find the specified Oracle Home.
    WARNING: KFOD not found at
    INFO: inventory location is/opt/oracle/app/oraInventory
    WARNING: KFOD not found at
    FINE: oracle.install.commons.util.Resource:Can't find resource for bundle oracle.install.asm.resource.ASMErrorResID, key oracle.install.asm.bean.ASMInputValidationErrorCode.hint
    SEVERE: [FATAL] [INS-30508] Invalid ASM disks.
    CAUSE: The disks [dev/oracleasm/disks/ASMDATA1, /dev/oracleasm/disks/ASMDATA2, /dev/oracleasm/disks/ASMDATA3] were not valid.
    ACTION: Please choose or enter valid ASM disks.
    INFO: Advice is ABORT
    INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
    INFO: Completed validating state <CreateASMDiskGroup>
    INFO: Terminating all background operations
    INFO: Terminated all background operations
    FINE: oracle.install.commons.util.Resource:Can't find resource for bundle oracle.install.commons.util.resource.ErrorCodeResourceBundle, key oracle.install.commons.util.exception.CommonErrorCode.hint
    INFO: Finding the most appropriate exit status for the current application
    INFO: Exit Status is -2
    INFO: Shutdown Oracle Grid Infrastructure
    INFO: Unloading Setup Driver
    Been stuck here for a couple days...
    My current direction is looking at the "WARNING: KFOD not found at" message...
    kfod does exist in the /tmp/OraInstall2012-01-12_04-40-31PM/ext/bin/kfod folder while the installation is running...so I'm not sure what to make of it.
    Let me know if anyone can shed some light here...
    Thanks in advance,
    Colby

    We managed to figure it out...
    It turns out that a previously failed -silent run of the OUI had left some Oracle files hanging about. The OUI not showing the ASM disks because they were associated to the failed installation. After removing 'ALL' the files from the failed installation and a reboot we were able to get through the full install successfully.
    Make sure you fully clean up after a failed install...
    cs

  • Oracle ASM disk group

    Hi,
    Having a multiple Oracle ASM disk group is more beneficial for Oracle database? if no why? if yes why?
    Any metalink note if have.
    thanks

    Any metalink note do you refer?What is your database version?
    Please see these docs.
    11g ASM New Feature [ID 429098.1]
    ASM 11g New Features - How ASM Disk Resync Works. [ID 466326.1]
    Thanks,
    Hussein

  • I have a PC and a need help to configure my external hard disk on my network. Thanks

    I have a PC and a need help to configure my external hard disk on my network. Thanks

    If you mean you wish to plug a USB drive into the Airport Extreme router (or TC not express) that is easy..
    The disk must be formatted FAT32.. as if.. stay away from FAT .. or HFS+ ie Mac OS extended Journaled.
    Format the disk on a Mac is best.. and even use GUID partition scheme not MBR.
    The PC has no issue writing and reading files because this is a network drive.. The PC does not write to the drive.. it writes files to the Airport OS which writes and reads the disk and passes the info using standard windows SMB.. To the windows computer it will be a Windows NT server.. FAT32 setup.
    If your setup is different.. to my hugely guessed assumptions.. give details.. always helps to have.. make and model.
    Make and model of disk.. make and model of router.. how the setup will be done.. what windows OS you run.. etc etc.
    As it stands your question could have nothing to do with apple at all.. other than you posted in a forum so I guess there is something apple in there somewhere.

  • Error: This disk needs to be repaired using the Recovery HD.  When I boot on Recovery and run verify disk, the error doesn't come anymore. Just when I run verify disk on normal mode. Anybody has seen this before?

    My Macbook Pro (Retina, 13-inch, Early 2013) has been freezing out of the blue probably once every two months. I restarted on safe mode, went to Disk Utility, repaired permissions and ran "Verify Disk" and got  the following:
    Invalid directory item count(It should be 114483 instead of 114484)
    File system check exit code is 8.
    Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
    Rebooted on Recovery mode and ran "Verify Disk" but the message didn't appear anymore, thus not letting me to access the "Recovery HD" procedure.
    When I restart normally and do the disk verification I get the same error.
    Has anybody come to something similar?
    Suggestions?

    I never  ever run a Verify Disk. I simple repair the disk drive and then the user partition(s).
    And do one or two Safe Boots.
    Also helpful to have two full backups: TimeMachine at least, plus a clone of your system drive and data.
    Install or clone the system to an external hard drive, repair that and then boot from it, check that everything works, repair the internal drive.
    You need to use Repair to TRIM an SSD.
    Lots of problems with Yosemite when updating install a new OS. Always better to backup, erase, install, and then use Setup Assistant to import and restore settings and files.
    Probably better to post in the MacBook Pro forum or better yet, in Yosemite forum.

  • Oracleasm cannot find asm disks on boot

    Hello!
    RAC 11.2.0.2 on SLES10.
    I have configured asmlib on a RAC system (multipath configured) and everything worked as a charm before booting node 2 in the cluster. Problem is that after reboot of node 2 i cannot see my asm disks anymore on that node. This only happens on node 2. I dont have this issue after rebooting node 1. However, if i do a manually "scandisks" on node 2 it sees the disks again and the cluster starts successfully..
    I cannot see any difference between the two nodes.. the asmlib rpm's matches the kernel version.
    oracle@prod2:~> uname -a
    Linux prod2 2.6.16.60-0.54.5-smp #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux
    oracle@prod2:~> rpm -qa |grep oracleasm
    oracleasm-support-2.1.4-1.SLE10
    oracleasm-2.6.16.60-0.54.5-smp-2.0.5-1.SLE10
    oracleasmlib-2.0.4-1.SLE10/etc/sysconfig/oracleasm looks like this:
    # This is a configuration file for automatic loading of the Oracle
    # Automatic Storage Management library kernel driver.  It is generated
    # By running /etc/init.d/oracleasm configure.  Please use that method
    # to modify this file
    # ORACLEASM_ENABELED: 'true' means to load the driver on boot.
    ORACLEASM_ENABLED=true
    # ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
    ORACLEASM_UID=oracle
    # ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
    ORACLEASM_GID=dba
    # ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
    ORACLEASM_SCANBOOT=true
    # ORACLEASM_SCANORDER: Matching patterns to order disk scanning
    ORACLEASM_SCANORDER="dm"
    # ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
    ORACLEASM_SCANEXCLUDE="sd"I would be grateful if anyone out there can shed some light on this issue..
    Thanks a bunch!

    Hi,
    I think you need to upgrade your powerpath version. If you are using clariion for your storage.

  • Migrating ASM disk from singlepath to multipath

    Hi,
    I need to migrate the single path for the SAN disks to a multipath access mode.
    Here is my environment :
    Oracle DB : 11gR2 Enterprise version (2 Node RAC)
    OS : Oracle Enterprise Linux 5
    DB file system : ASM disks with ASMLib
    disk used : SAN disk
    Multipath software : EMC Powerpath
    single path names are : /dev/sdb, /dev/sdc, .. etc.
    Multipath Name would be : /dev/emcpowera, /dev/emcpowerb etc.
    From different metalink document and google, I came up with the following steps for migrating the ASM disks from singlepath to multipath :
    (** Perform the below steps on both the nodes)
    1.     Open ASMLIB configuration file: /etc/sysconfig/oracleasm (Backup this file at this point)
    3.     Edit the variable ORACLEASM_SCANORDER to provide the prefix path of the multipath disk.
    For example:
    The multipath disk name would be /dev/emcpowera, /dev/emcpowerb etc. (Since we are using emc powerpath), set the ORACLEASM_SCANORDER variable as follows:
    ORACLEASM_SCANORDER="emcpower"
    4.     Edit the variable ORACLEASM_SCANEXCLUDE to exclude the single disks (/dev/sd*) from scan process.
    ORACLEASM_SCANEXCLUDE=”sd”
    5.     Reboot both the nodes.
    Are the above steps fine? Any addition/ modification needed ? Please advise.
    Raised an SR for this, but did not get a direct answer.
    Also. Do I need to set the ASM_DISKSTRING parameter to any specific value for my ASM instance? It is currently set to NULL.
    Thanks.

    Hi,
    no actually that's all there is to it.
    Since you use ASMLIB, the disks will be presented the same to ASM. So there is no need to change the DISCOVERY_STRING.
    Only thing I personally would do (for testing purposes) is the following:
    1.) Check before migrating that all disks are there (oracleasm listdisks), then
    2.) Disable the automatic startup of the crs stack (crsctl disable crs), that you can test everything (including reboot) without having the clustarstack start automatically.
    3.) If after the reboot the oracleasm listdisks sees all disks you are fine
    4.) Enable crs again (crsctl enable crs) and start the clusterstack (crsctl start crs).
    Regards
    Sebastian

  • ASM: cannot create asm disks - permission denied

    We cannot create ASM disks using the command:
    # /etc/init.d/oracleasm creatdisk ASMDISK1 /dev/mapper/mpathdp1
    Marking disk "ASMDISK1" as an ASM disk: [FAILED]
    The log (/var/log/oracleasm) has the following:
    Clearing disk header: done
    Disk "ASMDISK1" does not exist or is not instantiated
    Writing disk header: done
    Instantiating disk: oracleasm-instantiate-disk: Unable to create ASM disk "ASMDISK1": Permission denied
    failed
    Clearing disk header: done
    The command is being executed by the root user. Our environment is OEL6:
    [oracle@uxdbidbd1 mapper]$ uname -rm
    2.6.32-100.28.11.el6.x86_64 x86_64
    To install ASMLib we did the following:
    Installed the three packages:
    1.oracleasm-support-2.1.4-1.el5.x86_64.rpm
    2.oracleasmlib-2.0.4-1.el5.x86_64.rpm
    3.oracleasm-2.6.18-238.9.1.el5-debuginfo-2.0.5-1.el5.x86_64.rpm
    [root@uxdbidbd1 ~]# modprobe oracleasm
    [root@uxdbidbd1 ~]# /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 []: oracle
    Default group to own the driver interface []: oinstall
    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  ]
    [root@uxdbidbd1 ~]#
    [root@uxdbidbd1 ~]# /etc/init.d/oracleasm status
    Checking if ASM is loaded: yes
    Checking if /dev/oracleasm is mounted: yes
    Our SA partitioned the disk using fdisk:
    [root@uxdbidbd1 ~]# fdisk -l /dev/mapper/mpathd
    Disk /dev/mapper/mpathd: 52.4 GB, 52428800000 bytes
    255 heads, 63 sectors/track, 6374 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x4849251a
    Device Boot Start End Blocks Id System
    /dev/mapper/mpathdp1 1 6374 51199123+ 83 Linux
    Here are the owner/permissions:
    [oracle@uxdbidbd1 mapper]$ ls -al /dev/mapper/
    lrwxrwxrwx. 1 root root 7 Apr 22 14:58 mpathd -> ../dm-5
    brw-rw-r--. 1 oracle oinstall 253, 6 Apr 25 10:56 mpathdp1
    [oracle@uxdbidbd1 dev]$ ls -al /dev
    brw-rw----. 1 root disk 253, 5 Apr 22 15:45 dm-5
    drwxr-xr-x. 4 root root 0 Apr 22 14:58 oracleasm
    [oracle@uxdbidbd1 oracleasm]$ ls -al /dev/oracleasm
    total 0
    drwxr-xr-x. 4 root root 0 Apr 22 14:58 .
    drwxr-xr-x. 23 root root 7200 Apr 24 03:41 ..
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .check_iid
    drwxr-xr-x. 1 root root 0 Apr 22 14:58 disks
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .get_iid
    drwxrwx---. 1 oracle oinstall 0 Apr 22 14:58 iid
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_disk
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_version
    We ran an strace on the createdisk command that is failing and I noticed this in the output file:
    28830 mknod("/dev/oracleasm/disks/ASMDISK1", S_IFBLK|0600, makedev(253, 6)) = -1 EACCES (Permission denied)
    28830 write(2, "oracleasm-instantiate-disk: ", 28) = 28
    28830 write(2, "Unable to create ASM disk \"ASMDI"..., 56) = 56
    We changed /dev/oracleasm/disks to 777 in order to test but we got the same result. Do we need to adjust the permissions to all of the parent directories in the path (/dev/oracleasm/disks)? I've been looking around for anything related to permissions on /dev/oracleasm but the docs don't mention anything. Any help would be greatly appreciated.

    From what I understand, you should not set device permissions of /dev/oracleasm since oracleasm takes care of it according to /etc/init.d/oracleasm configure.
    The problem in your case seems to be that ASM refuses to initialize and write metadata to your device. Was the device previously used by ASM? ASM will fail to initialize a device that contains previous ASM metadata. To erase the device you will need to use the dd command, e.g. dd if=/dev/zero of=/dev/sdb. Both ASMLib and raw devices require the candidate disks to be partitioned before they can be accessed. To create a partition on /dev/sdb, for instance, type fdisk /dev/sdb and create a standard partition using the defaults. This will create /dev/sdb1 and you can try oracleasm createdisk again.
    You may try the above, but anyway, I was not sure how much you can trust your installation. The problem could also be that you installed the oracleasm kernel driver and asmlib software for OEL 5. Oracle Linux 6 includes an oracleasm kernel driver and as far as I remember you must not install another oracleasm kernel driver. Using modprob oracleasm and installing oracleasm support package using yum should do the trick. You may also need to download and install the asmlib package for the Oracle ASM grid install to see the ASM disks.

  • Please Help - When I try to add ASM Disk to ASM Diskgroup it crashes Server

    We are using a Pillar SAN and have LUNS Created and are using the following multipath device: (I'm a DBA more then anything else... but I am rather familiar with linux .... SAN Hardware not so much)
    Device Size Mount Point
    /dev/dpda1 11G /u01
    The Above device is working fine... Below are the ASM Disks being Created
    Device Size Oracle ASM Disk Name
    /dev/dpdb1 198G ORCL1
    /dev/dpdc1 21G SIRE1
    /dev/dpdd1 21G CART1
    /dev/dpde1 21G SRTS1
    /dev/dpdf1 21G CRTT1
    I try to create to the first ASM Disk
    /etc/init.d/oracleasm createdisk ORCL1 /dev/dpdb1
    Marking disk "ORCL1" as an ASM disk: [FAILED]
    So I check the oracleasm log:
    #cat /var/log/oracleasm
    Device "/dev/dpdb1" is not a partition
    I did some research and found that this is a common problem with multipath devices and to work around it you have to use asmtool
    # /usr/sbin/asmtool -C -l /dev/oracleasm -n ORCL1 -s /dev/dpdb1 -a force=yes
    asmtool: Device "/dev/dpdb1" is not a partition
    asmtool: Continuing anyway
    now I scan and list the disks
    # /etc/init.d/oracleasm scandisks
    Scanning the system for Oracle ASMLib disks: [  OK  ]
    # /etc/init.d/oracleasm listdisks
    ORCL1
    Here is whats going on in /var/log/messages when I run the oracleasm scandisks command
    # date
    Fri Aug 14 13:51:58 MST 2009
    # /etc/init.d/oracleasm scandisks
    Scanning the system for Oracle ASMLib disks: [  OK  ]
    cat /var/log/messages | grep "Aug 14 13:5"
    Aug 14 13:52:06 seer kernel: dpdb: dpdb1
    Aug 14 13:52:06 seer kernel: dpdc: dpdc1
    Aug 14 13:52:06 seer kernel: dpdd: dpdd1
    Aug 14 13:52:06 seer kernel: dpde: dpde1
    Aug 14 13:52:06 seer kernel: dpdf: dpdf1
    Aug 14 13:52:06 seer kernel: dpdg: dpdg1
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: printk: 30 messages suppressed.
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: sda : READ CAPACITY failed.
    Aug 14 13:52:06 seer kernel: sda : status=1, message=00, host=0, driver=08
    Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
    Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
    Aug 14 13:52:06 seer kernel:
    Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
    Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
    Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
    Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: Dev sda: unable to read RDB block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
    Aug 14 13:52:06 seer kernel: unable to read partition table
    Aug 14 13:52:06 seer kernel: SCSI device sdb: 21502464 512-byte hdwr sectors (11009 MB)
    Aug 14 13:52:06 seer kernel: sdb: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdb: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdb: sdb1
    Aug 14 13:52:06 seer kernel: SCSI device sdc: 421476864 512-byte hdwr sectors (215796 MB)
    Aug 14 13:52:06 seer kernel: sdc: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdc: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdc: sdc1
    Aug 14 13:52:06 seer kernel: SCSI device sdd: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdd: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdd: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdd: sdd1
    Aug 14 13:52:06 seer kernel: SCSI device sde: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sde: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sde: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sde: sde1
    Aug 14 13:52:06 seer kernel: SCSI device sdf: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdf: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdf: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdf: sdf1
    Aug 14 13:52:06 seer kernel: SCSI device sdg: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdg: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdg: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdg: sdg1
    Aug 14 13:52:06 seer kernel: SCSI device sdh: 2107390464 512-byte hdwr sectors (1078984 MB)
    Aug 14 13:52:06 seer kernel: sdh: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdh: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdh: sdh1
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
    Aug 14 13:52:06 seer kernel: Buffer I/O error on device sdi, logical block 0
    Aug 14 13:52:06 seer kernel: sdi : READ CAPACITY failed.
    Aug 14 13:52:06 seer kernel: sdi : status=1, message=00, host=0, driver=08
    Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
    Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
    Aug 14 13:52:06 seer kernel:
    Aug 14 13:52:06 seer kernel: sdi: test WP failed, assume Write Enabled
    Aug 14 13:52:06 seer kernel: sdi: asking for cache data failed
    Aug 14 13:52:06 seer kernel: sdi: assuming drive cache: write through
    Aug 14 13:52:06 seer kernel: sdi:end_request: I/O error, dev sdi, sector 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
    Aug 14 13:52:06 seer last message repeated 4 times
    Aug 14 13:52:06 seer kernel: Dev sdi: unable to read RDB block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
    Aug 14 13:52:06 seer kernel: unable to read partition table
    Aug 14 13:52:06 seer kernel: SCSI device sdj: 21502464 512-byte hdwr sectors (11009 MB)
    Aug 14 13:52:06 seer kernel: sdj: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdj: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdj: sdj1
    Aug 14 13:52:06 seer kernel: SCSI device sdk: 421476864 512-byte hdwr sectors (215796 MB)
    Aug 14 13:52:06 seer kernel: sdk: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdk: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdk: sdk1
    Aug 14 13:52:06 seer kernel: SCSI device sdl: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdl: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdl: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdl: sdl1
    Aug 14 13:52:06 seer kernel: SCSI device sdm: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdm: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdm: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdm: sdm1
    Aug 14 13:52:06 seer kernel: SCSI device sdn: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdn: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdn: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdn: sdn1
    Aug 14 13:52:06 seer kernel: SCSI device sdo: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdo: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdo: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdo: sdo1
    Aug 14 13:52:06 seer kernel: SCSI device sdp: 2107390464 512-byte hdwr sectors (1078984 MB)
    Aug 14 13:52:06 seer kernel: sdp: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdp: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdp: sdp1
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
    Aug 14 13:52:06 seer kernel: sdq : READ CAPACITY failed.
    Aug 14 13:52:06 seer kernel: sdq : status=1, message=00, host=0, driver=08
    Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
    Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
    Aug 14 13:52:06 seer kernel:
    Aug 14 13:52:06 seer kernel: sdq: test WP failed, assume Write Enabled
    Aug 14 13:52:06 seer kernel: sdq: asking for cache data failed
    Aug 14 13:52:06 seer kernel: sdq: assuming drive cache: write through
    Aug 14 13:52:06 seer kernel: sdq:end_request: I/O error, dev sdq, sector 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
    Aug 14 13:52:06 seer last message repeated 5 times
    Aug 14 13:52:06 seer kernel: Dev sdq: unable to read RDB block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
    Aug 14 13:52:06 seer kernel: unable to read partition table
    Aug 14 13:52:06 seer kernel: SCSI device sdr: 21502464 512-byte hdwr sectors (11009 MB)
    Aug 14 13:52:06 seer kernel: sdr: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdr: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdr: sdr1
    Aug 14 13:52:06 seer kernel: SCSI device sds: 421476864 512-byte hdwr sectors (215796 MB)
    Aug 14 13:52:06 seer kernel: sds: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sds: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sds: sds1
    Aug 14 13:52:06 seer kernel: SCSI device sdt: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdt: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdt: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdt: sdt1
    Aug 14 13:52:06 seer kernel: SCSI device sdu: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdu: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdu: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdu: sdu1
    Aug 14 13:52:06 seer kernel: SCSI device sdv: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdv: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdv: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdv: sdv1
    Aug 14 13:52:06 seer kernel: SCSI device sdw: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdw: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdw: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdw: sdw1
    Aug 14 13:52:06 seer kernel: SCSI device sdx: 2107390464 512-byte hdwr sectors (1078984 MB)
    Aug 14 13:52:06 seer kernel: sdx: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdx: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdx: sdx1
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
    Aug 14 13:52:06 seer kernel: sdy : READ CAPACITY failed.
    Aug 14 13:52:06 seer kernel: sdy : status=1, message=00, host=0, driver=08
    Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
    Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
    Aug 14 13:52:06 seer kernel:
    Aug 14 13:52:06 seer kernel: sdy: test WP failed, assume Write Enabled
    Aug 14 13:52:06 seer kernel: sdy: asking for cache data failed
    Aug 14 13:52:06 seer kernel: sdy: assuming drive cache: write through
    Aug 14 13:52:06 seer kernel: sdy:end_request: I/O error, dev sdy, sector 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
    Aug 14 13:52:06 seer last message repeated 5 times
    Aug 14 13:52:06 seer kernel: Dev sdy: unable to read RDB block 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
    Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
    Aug 14 13:52:06 seer kernel: unable to read partition table
    Aug 14 13:52:06 seer kernel: SCSI device sdz: 21502464 512-byte hdwr sectors (11009 MB)
    Aug 14 13:52:06 seer kernel: sdz: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdz: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdz: sdz1
    Aug 14 13:52:06 seer kernel: SCSI device sdaa: 421476864 512-byte hdwr sectors (215796 MB)
    Aug 14 13:52:06 seer kernel: sdaa: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdaa: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdaa: sdaa1
    Aug 14 13:52:06 seer kernel: SCSI device sdab: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdab: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdab: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdab: sdab1
    Aug 14 13:52:06 seer kernel: SCSI device sdac: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdac: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdac: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdac: sdac1
    Aug 14 13:52:06 seer kernel: SCSI device sdad: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdad: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdad: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdad: sdad1
    Aug 14 13:52:06 seer kernel: SCSI device sdae: 43006464 512-byte hdwr sectors (22019 MB)
    Aug 14 13:52:06 seer kernel: sdae: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdae: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdae: sdae1
    Aug 14 13:52:06 seer kernel: SCSI device sdaf: 2107390464 512-byte hdwr sectors (1078984 MB)
    Aug 14 13:52:06 seer kernel: sdaf: Write Protect is off
    Aug 14 13:52:06 seer kernel: SCSI device sdaf: drive cache: write through w/ FUA
    Aug 14 13:52:06 seer kernel: sdaf: sdaf1
    Aug 14 13:52:06 seer kernel: scsi_wr_disk: unknown partition table
    Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sda, sector 0
    Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdi, sector 0
    Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdq, sector 0
    Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdy, sector 0
    Here's some extra info:
    # /sbin/blkid | grep asm
    /dev/sdc1: LABEL="ORCL1" TYPE="oracleasm"
    /dev/sdk1: LABEL="ORCL1" TYPE="oracleasm"
    /dev/sds1: LABEL="ORCL1" TYPE="oracleasm"
    /dev/sdaa1: LABEL="ORCL1" TYPE="oracleasm"
    /dev/dpdb1: LABEL="ORCL1" TYPE="oracleasm"
    I have learned that by excluding devices in the oracleasm configuration file I eliminate those I/O errors in /var/log/messages
    # cat /etc/sysconfig/oracleasm
    # This is a configuration file for automatic loading of the Oracle
    # Automatic Storage Management library kernel driver. It is generated
    # By running /etc/init.d/oracleasm configure. Please use that method
    # to modify this file
    # ORACLEASM_ENABELED: 'true' means to load the driver on boot.
    ORACLEASM_ENABLED=true
    # ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
    ORACLEASM_UID=oracle
    # ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
    ORACLEASM_GID=oinstall
    # ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
    ORACLEASM_SCANBOOT=true
    # ORACLEASM_SCANORDER: Matching patterns to order disk scanning
    ORACLEASM_SCANORDER="dp sd"
    # ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
    ORACLEASM_SCANEXCLUDE="sdc sdk sds sdaa sda"
    # ls -la /dev/oracleasm/disks/
    total 0
    drwxr-xr-x 1 root root 0 Aug 14 10:47 .
    drwxr-xr-x 4 root root 0 Aug 13 15:32 ..
    brw-rw---- 1 oracle oinstall 251, 33 Aug 14 13:46 ORCL1
    Now I can go into dbca to create the ASM instance, which starts up fine...  create a new diskgroup, I see ORCL1 as a provision ASM disk I select it ...  Click OK
    CRASH!!!  Box hangs have to reboot it....
    I have gotten myself to exactly the same point right before clicking OK and here is what is in the ASM alertlog so far
    Fri Aug 14 14:42:02 2009
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/db_1/dbs/arch
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =0
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.6.0.
    Using parameter settings in server-side spfile /u01/app/oracle/product/11.1.0/db_1/dbs/spfile+ASM.ora
    System parameters with non-default values:
    large_pool_size = 12M
    instance_type = "asm"
    diagnostic_dest = "/u01/app/oracle"
    Fri Aug 14 14:42:04 2009
    PMON started with pid=2, OS id=3300
    Fri Aug 14 14:42:04 2009
    VKTM started with pid=3, OS id=3302 at elevated priority
    VKTM running at (20)ms precision
    Fri Aug 14 14:42:04 2009
    DIAG started with pid=4, OS id=3306
    Fri Aug 14 14:42:04 2009
    PSP0 started with pid=5, OS id=3308
    Fri Aug 14 14:42:04 2009
    DSKM started with pid=6, OS id=3310
    Fri Aug 14 14:42:04 2009
    DIA0 started with pid=7, OS id=3312
    Fri Aug 14 14:42:04 2009
    MMAN started with pid=8, OS id=3314
    Fri Aug 14 14:42:04 2009
    DBW0 started with pid=9, OS id=3316
    Fri Aug 14 14:42:04 2009
    LGWR started with pid=6, OS id=3318
    Fri Aug 14 14:42:04 2009
    CKPT started with pid=10, OS id=3320
    Fri Aug 14 14:42:04 2009
    SMON started with pid=11, OS id=3322
    Fri Aug 14 14:42:04 2009
    RBAL started with pid=12, OS id=3324
    Fri Aug 14 14:42:04 2009
    GMON started with pid=13, OS id=3326
    ORACLE_BASE from environment = /u01/app/oracle
    Fri Aug 14 14:42:04 2009
    SQL> ALTER DISKGROUP ALL MOUNT
    Fri Aug 14 14:42:41 2009
    At this point I don't want to click the OK until I am sure someone is in the office to reboot the machine manually if I do hang it again....  I hung it twice yesterday, however I did not have the devices excluded in the oracleasm configuration file as i do now
    Edited by: user10193377 on Aug 14, 2009 3:23 PM
    Well Clicking OK hun it again and I am waiting to get back into it, to see what new information might be gleened
    Does anyone have any ideas on what to check or where to look?????    Will update more once I can log back in

    Hi Mark,
    It looks like something is not correct with your raw device partition based on the error messages:
    Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
    Aug 14 13:52:06 seer kernel:
    Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
    Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
    Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
    Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
    It could be a number of things. I would check with your vendor and Oracle support to see if the multipath software drive is supported and if there is a potential workaround for ASM. Sorry this is not quite the solution, but its what jumps to mind based on issues with multipath software and storage vendors for ASM with Linux and Oracle. Have you checked the validation matrix available on Metalink?
    Cheers,
    Ben

Maybe you are looking for

  • Uneditable art on tracks with missing art

    Hi, I have a small problem with some of my albums, for one or two random tracks I am unable to add / edit arkwork... if I right click on the track "Get Info", I am given four tabs - Summary, Info, Sorting & Options... usually there is a fith tab for

  • Mds (spotlight) crash logs - what does this mean?

    I see a bunch of files under the CrashReporter log called mds2011-04-14-xxxxxxlocalhost.crash that look like this: Process: mds [6104] Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Suppor

  • How to replicate FP bank configuration

    In my application I use 14 (fourteen) FieldPoint banks exactly alike: FP-1601+DO-401+DI-301+AI-100+TC-120. I would like to configure one bank and then, except for the name and IP address, just replicate that configuration onto the other 13. How do I

  • Unity 4.2.1 Bulk Edit Error

    Hi there, I just recently upgraded my Unity Voicemail Only server from 3.1.3 to 4.2.1. Everything is working correctly, but I have one issue. Normally, I use the Bulk Edit tool to set a Subscriber's voicemail to loopback to self on an Error during a

  • Error while installing TREX .

    Hi all, iam installing TREX 6.1 sp14. iam getting error in step II that is , Installing Python software and resources. the log is ERROR 2006-02-15 10:22:21 FSL-06002  Error 2 (The system cannot find the file specified.) in execution of a 'CreateProce