ASM disks in OUI
OS Windows 2008 R2.
I had to uninstall my Oracle grid.
I try to re-install, and when I get to the ASM, it doesn't find any disks.
I re-stamped them using asmtoolg, and still the same.
Thanks in advance!
Hi,
Not on Windows.
On OUI click "Change Discovery Path"
if the parameter ASM_DISKTRING is empty try set to "\\.\orcldisk*"
if the parameter ASM_DISKTRING already have some value unconfigure and leave the parameter empty, it will assume the default value.
Regards,
Levi Pereira
Similar Messages
-
I need to install a Oracle Database in order to install Enterprise Manager Cloud Control 12c.
Need the database to use a ASM disk.
I used the following command to create the disk, per the Oracle Database Installation Guide.
#/usr/sbin/oracleasm createdisk DISK1 /dev/sdd1
#oracleasm listdisks
DISK1
However, when running the OUI for Oracle Database 12c (understand 11.2.0.3 is certified for Cloud Control), step 7
errors INS-30517 when attempting to select "Oracle Automatic Storage Management" for "Storage type".
Researched the error at this location but no cause or action was provided.
http://docs.oracle.com/cd/E16655_01/server.121/e26079/common_errormessages.htm
INS-30517: Automatic Storage Management software is not configured on this system.
The database install guide states that I need to ensure the "disk discovery string" is set the "ORCL:*" or is left empy ("") so the installer discovers these disks.
It doesn't show how to confirm or change the settings.
At this point I'm at a stopping point.All ASMLib installations require the oracleasmlib and oracleasm-support packages. The oracleasm kernel driver is included in the Oracle UEK kernel. Perhaps you are missing the oracleasmlib package. You can download it from:
Oracle Linux: Oracle ASMLib | Oracle Technology Network
Oracleasmlib is not necessary for ASM to work, but it contains software necessary for Linux oracleasm, including the /usr/sbin/oracleasm-discover utility, which the Oracle installer used in the previous 11g version to detect available ASM volumes. -
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,
ColbyWe 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 -
Why the ASM disks can't be used again?
Platform: Suse9(2.6.5-7smp)Linux x86_64, Oracle10g(10.1.0.3) RAC with ASM on 8 nodes and 30TB raw disks.
Problem:
In the first time, we created a db with a ASM Disk Group named RAC_DATA. But because of some errors we decided uninstall them. The uninstallation steps included removing all db and asm instances, rac software and crs software by dbca and oui. And cleared the shared ocr.crs and vote.crs in device raw1 and raw2.
In the second time, we installed the crs and rac successfully. But when we ran dbca to recreate a database, all asm disks are unavailable, they all still belongs to the RAC_DATA group . But we have deleted RAC_DATA group in the uninstallation. What's more, we removed all in $ORACLE_HOME, $ORACLE_BASE/admin and $ORACLE_CRS_HOME.
I don't know where the information about asm disks group stored. How can I clear it completely and reuse these disks them again.The problem is the that ASM metadata still exists. You can use the dd command to clear the metadata from the ASM disks.
dd if=/dev/zero of=/dev/raw/raw1 bs=8192 count=12800
Substitute the name of your device for /dev/raw/raw1 above. For further information see metalink note 26848.1 Re-Creating ASM instances and Diskgroups. -
INS-30508 Invalid ASM disks on 11.2.0.3 OL 6.2 grid standalone install
New set of Dell servers R710s running OL 6.2 redhat compatible kernel
$ uname -a
Linux seoltpo-02 2.6.32-220.el6.x86_64
Connected to EMC VNX5500 and using powerpath 5.6.0. Not a rac environment ... doing 11.2.0.3 base install of grid infrastructure for a standalone server.
Not using ASMLIB.
Disk permissions are correct as grid install begins ...
brw-rw---- 1 grid oinstall 120, 704 Jul 26 21:18 emcpoweras
brw-rw---- 1 grid oinstall 120, 720 Jul 26 21:18 emcpowerat
brw-rw---- 1 grid oinstall 120, 736 Jul 26 21:18 emcpowerau
brw-rw---- 1 grid oinstall 120, 752 Jul 26 21:18 emcpowerav
brw-rw---- 1 grid oinstall 120, 768 Jul 26 21:18 emcpoweraw
brw-rw---- 1 grid oinstall 120, 784 Jul 26 21:18 emcpowerax
brw-rw---- 1 grid oinstall 120, 800 Jul 26 21:18 emcpoweray
brw-rw---- 1 grid oinstall 120, 816 Jul 26 21:18 emcpoweraz
GUI installer sees the powerpath LUNs after changing the Disk Discovery path ... for example ....
INFO: ... discoveryString = /dev/emcpower*
INFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpower*']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing 40960 CANDIDATE /dev/emcpoweras grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerat grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerau grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerav grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraw grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerax grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweray grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraz grid oinstall
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweru
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweru"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
*** Of course there are other LUNs not going to be part of ASM disk groups so it cannot read all of them initially.
Somehow after first looking at the disks and seeing them the first time the permissions are changed back on the disks over to root:root as soon as the GUI sees the disks.
You select the disks that you want in the GUI ( but the permissions have been changed already ) so click Next and wham INS 30508 ...
The Install log shows that kfod is apparently scanning the disks a bunch of time ... but before the error appears install log sees that permissions have changed.
Somehow actions caused from running the GUI are changing the permissions? Something is wrong somewhere ... powerpath ? 11.2.0.3 on this kernel version ? Seems very bizarre ...
NFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpoweras','/dev/emcpowerat','/dev/emcpowerau','/dev/emcpowerav','/dev/emcpoweraw','/dev/emcpowerax','/dev/emcpoweray','/dev/emcpoweraz']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraz
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraz"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: The process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod exited with code 0
INFO: Waiting for output processor threads to exit.
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweray
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweray"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerax
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerax"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraw
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraw"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerav
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerav"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerau
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerau"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerat
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerat"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweras
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweras"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Output processor threads exited.
SEVERE: [FATAL] [INS-30508] Invalid ASM disks.
CAUSE: The disks [dev/emcpoweras, /dev/emcpowerat, /dev/emcpowerau, /dev/emcpowerav, /dev/emcpoweraw, /dev/emcpowerax, /dev/emcpoweray, /dev/emcpoweraz] 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
INFO: Transition aborted
INFO: Rolled back to state <CreateASMDiskGroup>
Is there some kind of configuration steps I am missing somewhere?
Yeah I know probably going to have to open an SR here but some of you guys around here are pretty sharp. Can I attach the whole install log here somehow?Well I am not exactly opposed to udev rules for the powerpath devices ... not that I know what that is exactly ... if this can fix my problem.
I found an example or two from google ...
It looks like on my OL 6.2 system there is a difference in the files ( rules I guess ) under /etc/udev/rules.d
# *** OL 5.7 system below
$ ls -ltr
total 232
-rw-r--r-- 1 root root 1088 Jun 6 2007 60-pcmcia.rules
-rw-r--r-- 1 root root 58016 Jun 6 2007 60-libsane.rules
-rw-r--r-- 1 root root 2319 Jul 14 2008 bluetooth.rules
-rw-r--r-- 1 root root 114 Nov 5 2008 90-alsa.rules
-rw-r--r-- 1 root root 1823 Nov 5 2008 85-pcscd_ccid.rules
-rw-r--r-- 1 root root 316 Dec 8 2010 60-raw.rules
-rw-r--r-- 1 root root 82 Jan 13 2011 90-hal.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r-- 1 root root 292 May 11 2011 98-kexec.rules
-rw-r--r-- 1 root root 143 Jun 7 2011 60-net.rules
-rw-r--r-- 1 root root 331 Jun 9 2011 90-ib.rules
-rw-r--r-- 1 root root 992 Jul 8 2011 40-multipath.rules
-rw-r--r-- 1 root root 9366 Jul 22 2011 60-wacom.rules
-rw-r--r-- 1 root root 107 Jul 22 2011 95-pam-console.rules
-rw-r--r-- 1 root root 61 Jul 22 2011 90-dm.rules
-rw-r--r-- 1 root root 471 Jul 22 2011 51-hotplug.rules
-rw-r--r-- 1 root root 16732 Jul 22 2011 50-udev.rules
-rw-r--r-- 1 root root 515 Jul 22 2011 05-udev-early.rules
-rw-r--r-- 1 root root 175 Jul 22 2011 88-clock.rules
# *** OL 6.2 system below
$ ls -ltr
total 64
# *** OL 6.2 system below
$ ls -ltr
total 64
-rw-r--r--. 1 root root 1914 Apr 27 2010 85-pcscd_ccid.rules
-rw-r--r--. 1 root root 320 Jul 2 2010 90-alsa.rules
-rw-r--r--. 1 root root 1060 Jul 24 2010 60-pcmcia.rules
-rw-r--r--. 1 root root 1652 Nov 20 2010 60-fprint-autosuspend.rules
-rw-r--r--. 1 root root 2486 Dec 23 2010 97-bluetooth-serial.rules
-rw-r--r-- 1 root root 935 Mar 7 2011 95-dataeng-udev.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r--. 1 root root 706 Mar 29 2011 56-hpmud_support.rules
-rw-r--r--. 1 root root 6858 Mar 29 2011 40-hplip.rules
-rw-r--r--. 1 root root 83 May 20 2011 90-hal.rules
-rw-r--r--. 1 root root 316 Oct 13 2011 60-raw.rules
-rw-r--r--. 1 root root 54 Dec 7 2011 99-fuse.rules
-rw-r--r--. 1 root root 292 Dec 7 2011 98-kexec.rules
-rw-r--r--. 1 root root 53 Dec 7 2011 91-drm-modeset.rules
-rw-r--r--. 1 root root 789 Jul 19 07:28 70-persistent-cd.rules
??? So no file 50-udev.rules ... in the 6.2 system ??? But tons of stuff in the 5.7 system ... -
Reformatting ASM disks without ASM available
Hello Everyone,
In a test environment I recently built a single instance Oracle 11G database using ASM to manage database storage disks. The O/S is HP-UX v11.31 and the ASM disks are LUNs presented from a SAN. For a number of reasons I have had to rebuild this environment again from scratch, the O/S partition has been rebuilt and I have installed Oracle 11G again. However, when I now come to create & configure my ASM instance it does not find any candidate disks. I believe this is because those disks still have ASM formatting from the previous 'life' of the environment and the Diskgroups were not dropped , or the disks 'wiped' prior to rebuilding the O/S partition.
My problem is therefore - How can I 'reformat' the disks for reuse so that they will appear as candidates during ASM configuration, given the fact that I no longer have any ASM instance in existence. I'm guessing that the answer maybe to run some HP-UX O/S level commands to do this ?
Any advice or suggestion would be much appreciated !
Thanks,
ShaunHi,
Thanks very much for this. I've run the command against the affected SAN disks and it has worked. All disks now appear as candidates when I run ASM configuration through OUI.
Thanks again,
Shaun -
Asm disk removed taking too much time to boot
hi
a local machine is configured with ASM by oracleasm with a total disk.As it was a training purpose so i have removed the disk eg /dev/sdb bluntly ie. just removing it from box.now i tried fsck -c -c -f /dev/ in rescue mode its didnot worked even not mounting the /mnt/sysimage.It claims for ext2fs error and mounting the fs etc.
Then after lots of days has gone.i fed up with this issues and reinstalled OS.
but my question is what exactly to do?obviously re-installation is not the exact way to do.
regardsIf the +/dev/sdb+ was an ASM disk, then it should not impact the o/s when it is removed. ASM instance itself will fail with an error saying something like it was not able to mount the disk group.
If your system failed to boot correctly after this disk was removed, then +/dev/sdb+ contained more than just ASM data.
We dynamically add and remove ASM (multipath'ed) disks via kpartx - while o/s is running. No reboot. No problems.
I fail to see how a ASM disk could cause the type of problems you describe - unless it was more than just a disk used by ASM alone. -
Questions on asm disk discovery:
Questions on asm disk discovery:
1)What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) Which one of the above two finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
Thanks.From my understanding all disk you see in /dev/oracleasm/disks are the disks in your system that been discovered by asmlib at discovery stage.
Currently, due to bug 13465545, ASM instance will discover disks from both locations, ASM_DISKSTRING and gpnp profile, which can cause some mess in disk representation for asm. You can check the settings using asmcmd command: dsget, and set to be the same using dsset.
I think its more secure to set ASM_DISKSTRING to only the disks used by asm instance.
ASMCMD> dsget
Regards
Ed -
Questions on asm disk discover:
Questions on asm disk discover:
1)What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) which one finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we do not rely on the path the discover the asmlib
disks. asm_diskstring='ORCL:*' will identify the right disks. I am not sure if setting 'ORCL:*' is the most economic way as I am not sure if Oracle will have to scan all the disks
on the OS and probe the disks that it has rigths to determine which disks belong to ASM. If Oracle has to screen all the disks in this way, then I think setting
asm_diskstring='<path_to_asmlib_disk>' will be much faster. However, this will be open to the persistent problem. Is my understanding correct?
Thanks.Questions on asm disk discovery:
1)What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) Which one of the above two finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
Thanks. -
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 inHi 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 -
ASM Disk preparation for Datafiles and FRA in Oracle 10g RAC Inst
Dear Friends,
Please clarify wheteher the below method is correct to confiure ASM disks for Datafiles and FRA
Partitions provided by IT team for OCR and Voting Disk
/dev/sda1 - 150 GB (For +DATA)
/dev/sda2 - 100 GB (For +FRA)
OS : RHEL 5.6 (64 Bit)
kernel version = 2.6.18-238.el5
Steps:(Node1)
1) Install the RPM's for ASM
rpm -Uvh oracleasm-support-2.1.7-1.el5.x86_64.rpm
rpm -Uvh oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
rpm -Uvh oracleasmlib-2.0.4-1.el5.x86_64.rpm
2) Configure ASM
/etc/init.d/oracleasm configure
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
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
3) Cretae ASM Disk
/etc/init.d/oracleasm createdisk DISK1 /dev/sda1
/etc/init.d/oracleasm createdisk DISK2 /dev/sda2
4)/etc/init.d/oracleasm status
5)/etc/init.d/oracleasm scandisks
6)/etc/init.d/oracleasm listdisks
7) Nothing to perform on Node2
8) In dbca choose ASM and map the DISK1 for datafiles and DISK2 for FRA
Please confirm the above steps are right?if not please clarify
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?
Please refer any document / Metalink ID for the above complete process
Can i have ASM and oracle DB binary in the same home
Regards,
DBuser564706 wrote:
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?for asm disk created with oracleasm discovery path variable is ORCL:*
Please refer any document / Metalink ID for the above complete processhttp://docs.oracle.com/cd/B19306_01/install.102/b14203/storage.htm#BABIFHAB
Can i have ASM and oracle DB binary in the same homeyes. unless you want job role seperation or plan to run multiple versions of oracle homes
>
Regards,
DB -
Error while creating asm disk group
i am trying to convert my database SRAVAN as an ASM instance.
so do i need to set ORACLE_SID=+ASM???? r else it wil be SRAVAN??
I WAS ENDED UP WITH FOLLOWING ERRORS WHILE CREATING DISK GROUP.
guyz please do help me
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK '/u04/app/oracle/product/asmdisks/disk1'
5 FAILGROUP ctlr2
6 DISK '/u04/app/oracle/product/asmdisks/disk2';
CREATE DISKGROUP dgroup1
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk2' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk2'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk1' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk1'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
[oracle@sierra200 dbs]$ cd /u04/app/oracle/product/asmdisks
[oracle@sierra200 asmdisks]$ ls -ltr
total 205008
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:42 disk1
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:47 disk2
Thanks & Regards
Sravan DalavaiLooks like you are asking ASM to use plain files. Have you used the Device Loopback (losetup) a d made the emulate raw devices?
http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_20.shtml -
How to find the physical path of the ASM disks?
I am in a dilemma on how to find out the physical path of the ASM disks. I tried the following query, but as you can see it is not providing me the physical path of the LUN. This is a 2 node 10.2.0.4 RAC Cluster using asmlib package.
col name format a20
col path format a20
col label format a20
select name, path, label from v$asm_disk;
NAME PATH LABEL
ORCL:ASM103 ASM103
ORCL:ASM104 ASM104
ORCL:ASM117 ASM117
ASM101 ORCL:ASM101 ASM101
ASM102 ORCL:ASM102 ASM102
ASM105 ORCL:ASM105 ASM105
ASM106 ORCL:ASM106 ASM106
ASM107 ORCL:ASM107 ASM107
ASM108 ORCL:ASM108 ASM108
ASM109 ORCL:ASM109 ASM109
ASM110 ORCL:ASM110 ASM110
NAME PATH LABEL
ASM111 ORCL:ASM111 ASM111
ASM112 ORCL:ASM112 ASM112
ASM113 ORCL:ASM113 ASM113
ASM114 ORCL:ASM114 ASM114
ASM115 ORCL:ASM115 ASM115
ASM118 ORCL:ASM118 ASM118
ASM119 ORCL:ASM119 ASM119
ASM120 ORCL:ASM120 ASM120
ASM121 ORCL:ASM121 ASM121
ASM122 ORCL:ASM122 ASM122
ASM123 ORCL:ASM123 ASM123
NAME PATH LABEL
ASM124 ORCL:ASM124 ASM124
ASM125 ORCL:ASM125 ASM125
ASM126 ORCL:ASM126 ASM126
ASM127 ORCL:ASM127 ASM127
ASM302 ORCL:ASM302 ASM302
ASM303 ORCL:ASM303 ASM303
ASM304 ORCL:ASM304 ASM304
ASM305 ORCL:ASM305 ASM305
ASM306 ORCL:ASM306 ASM306
ASM307 ORCL:ASM307 ASM307
32 rows selected.
Any help will be appreciated.
--MMhi
use the following linux command as root:
$oracleasm listdisks
hth -
Want to move datafiles, controlfiles, redolog on new ASM Disks (11gR2 RAC)
Hi Guys,
Setup: Two Node 11gR2 (11.2.0.1) RAC on RHEL 5.4
Existing disks are from Old SAN & New Disks are from New SAN.
Can I move all datafiles (+DATA), controlfiles (+CTRL), redolog (+REDO) on new ASM Disks by adding disks in is same Diskgroup & dropping older disks from existing Diskgroup taking advantage of ASM Re-balancing Feature.
1) add required disks in the DATA Diskgroups,
ALTER DISKGROUP DATA ADD DISK
'/dev/oracleasm/disks/NEWDATA3' NAME NEWDATA_0003,
'/dev/oracleasm/disks/NEWDATA4' NAME NEWDATA_0004,
'/dev/oracleasm/disks/NEWDATA5' NAME NEWDATA_0005
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
2) When rebalance completes, drop the old disks.
ALTER DISKGROUP DATA DROP DISK
NEWDATA_0000,
NEWDATA_0001
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
3) Do it same for Redo log groups & Controlfile Diskgroups.
I hope, I could do this Activity, even if database is Up. is there possibility of Database block Corruption ??? (or is it necessary to perform above steps when database is down)
Would be appreciated, your quick responses on the same.
It's an urgent requirement. Thanks.
Regards,
ManishManish Nashikkar wrote:
Hi Guys,
Setup: Two Node 11gR2 (11.2.0.1) RAC on RHEL 5.4
Existing disks are from Old SAN & New Disks are from New SAN.
Can I move all datafiles (+DATA), controlfiles (+CTRL), redolog (+REDO) on new ASM Disks by adding disks in is same Diskgroup & dropping older disks from existing Diskgroup taking advantage of ASM Re-balancing Feature.
1) add required disks in the DATA Diskgroups,
ALTER DISKGROUP DATA ADD DISK
'/dev/oracleasm/disks/NEWDATA3' NAME NEWDATA_0003,
'/dev/oracleasm/disks/NEWDATA4' NAME NEWDATA_0004,
'/dev/oracleasm/disks/NEWDATA5' NAME NEWDATA_0005
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
2) When rebalance completes, drop the old disks.
ALTER DISKGROUP DATA DROP DISK
NEWDATA_0000,
NEWDATA_0001
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
3) Do it same for Redo log groups & Controlfile Diskgroups.
I hope, I could do this Activity, even if database is Up. is there possibility of Database block Corruption ??? (or is it necessary to perform above steps when database is down)
Would be appreciated, your quick responses on the same.
It's an urgent requirement. Thanks.
Regards,
Manish
Hi Manish,
Yes you can do that by adding new disk to existing diskgroup and delete old diskgroup. The good thing is this can be done online however you need to make sure the rebalance power is meet your business time, higher rebalance power is faster to rebalance to complete however it also will consume more resources
Cheers -
Difference between ASM Disk Group, ADVM Volume and ACFS File system
Q1. What is the difference between an ASM Disk Group and an ADVM Volume ?
To my mind, an ASM Disk Group is effectively a logical volume for Database files ( including FRA files ).
11gR2 seems to have introduced the concepts of ADVM volumes and ACFS File Systems.
An 11gR2 ASM Disk Group can contain :
ASM Disks
ADVM volumes
ACFS file systems
Q2. ADVM volumes appear to be dynamic volumes.
However is this therefore not effectively layering a logical volume ( the ADVM volume ) beneath an ASM Disk Group ( conceptually a logical volume as well ) ?
Worse still if you have left ASM Disk Group Redundancy to the hardware RAID / SAN level ( as Oracle recommend ), you could effectively have 3 layers of logical disk ? ( ASM on top of ADVM on top of RAID/SAN ) ?
Q3. if it is 2 layers of logical disk ( i.e. ASM on top of ADVM ), what makes this better than 2 layers using a 3rd party volume manager ( eg ASM on top of 3rd party LVM ) - something Oracle encourages against ?
Q4. ACFS File systems, seem to be clustered file systems for non database files including ORACLE_HOMEs, application exe's etc ( but NOT GRID_HOME, OS root, OCR's or Voting disks )
Can you create / modify ACFS file systems using ASM.
The oracle toplogy diagram for ASM in the 11gR2 ASM Admin guide, shows ACFS as part of ASM. I am not sure from this if ACFS is part of ASM or ASM sits on top of ACFS ?
Q5. Connected to Q4. there seems to be a number of different ways, ACFS file systems can be created ? Which of the below are valid methods ?
through ASM ?
through native OS file system creation ?
through OEM ?
through acfsutil ?
my head is exploding
Any help and clarification greatly appreciated
JimQ1 - ADVM volume is a type of special file created in the ASM DG. Once created, it creates a block device on the OS itself that can be used just like any other block device. http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000
Q2 - the asm disk group is a disk group, not really a logical volume. It combines attributes of both when used for database purposes, as the database and certain other applications know how to talk "ASM" protocol. However, you won't find any general purpose applications that can do so. In addition, some customers prefer to deal directly with file systems and volume devices, which ADVM is made to do. In your way of thinking, you could have 3 layers of logical disk, but each of them provides different attributes and characteristics. This is not a bad thing though, as each has a slightly different focus - os file system\device, database specific, and storage centric.
Q3 - ADVM is specifically developed to extend the characteristics of ASM for use by general OS applications. It understands the database performance characteristics and is tuned to work well in that situation. Because it is developed in house, it takes advantage of the ASM design model. Additionally, rather than having to contact multiple vendors for support, your support is limited to calling Oracle, a one-stop shop.
Q4 - You can create and modify ACFS file systems using command line tools and ASMCA. Creating and modifying logical volumes happens through SQL(ASM), asmcmd, and ASMCA. EM can also be used for both items. ACFS sits on top of ADVM, which is a file in an ASM disk group. ACFS is aware of the characteristics of ASM\ADVM volumes, and tunes it's IO to make best use of those characteristics.
Q5 - several ways:
1) Connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out. This creates an ADVM volume. Then, format the volume using 'mkfs' (*nix) or acfsformat (windows).
2) Use ASMCA - A gui to create a volume and format a file system. Probably the easiest if your head is exploding.
3) Use 'asmcmd' to create a volume, and 'mkfs' to format the ACFS file system.
Here is information on ASMCA, with examples:
http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348
Information on command line tools, with examples:
Basic Steps to Manage Oracle ACFS Systems
Maybe you are looking for
-
Mini display port to composite?
I'm a video DJ and have gotten tired of lugging around 2 DVJs, 2 mixers, and a case of DVDs to my gigs, so I decided to get a MacBook and join the ranks of the laptop DJs. I'm really starting to regret that decision. After dropping almost 3 grand o
-
Lenovo a3500-fl 4.4 update problem
so since i updated my tablet to 4.4. my tablet wont work with my router at home. it worked perfectly fine before. i used it for a few weeks before updating it with no issues. the wifi does work in it. i can tether my phone to my table and it works ju
-
Removed layouts folder but still "Restoring the window layout"
MY ORIGINAL PROBLEM All my Final Cut Pro X files are save on my external hard drive. When I open FCP with my hard drive plugged in, FCP says "Restoring the window layout" and a grey background appears. If I open FCP without my harddrive and then plug
-
Itunes is no longer recognizing my old iphone. Help!
itunes is no longer recognizing my old iphone. help!
-
RFC to pull the Idoc's from FTP
Hey, Is there any standard RFC to pull the IDOCs from an FTP server into the R3. Please help.