Missing ASM Disk.
we had a crash on our server and now when I run /et/init.d/oracleasm listdisks, it doesn't find anything. /dev/oracleasm/disks is empty too.
However, when I try and create a new disks it states dev/sde1 is already labeled an ASM device.
Any suggestions?
There are no rows in v$asm_diskgroup and when I try and startup +ASM1, I get the following error:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "SPS"
The disk is no longer present under /dev/oracleasm/disks, however, I am unable to create a new one (i.e. /etc/init.d/oracleasm createdisk DATA /dev/sde1) because it says /dev/sde1 is already labeled as an ASM disk.
Similar Messages
-
ORA-15042: ASM disk "2" is missing from group number "1"
Hi,
I'm working on an Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Automatic Storage Management option.
Into the ASM I had 3 diskgroups:
- ARCHIVELOG (4 disks)
- ONLINELOG (1 disks)
- DATA (10 disks)
When I try to startup the ASM instance I got:
A-15042: ASM disk "2" is missing from group number "1"The diskgroup won't be mounted.
I would like to remove that disk and later add a new one.
I can I do that?
I'm not able to mount the ARCHIVELOG diskgroup.
I tried the command
SQL> alter diskgroup archivelog drop disk ARCH3 force;
alter diskgroup archivelog drop disk ARCH3 force
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15001: diskgroup "ARCHIVELOG" does not exist or is not mountedThanks in advance,
Samuel
Edited by: Samuel Rabini on Jan 10, 2012 4:11 PMAs that database is on AWS, I tried this:
- drop diskgroup archivelog
- detach of those 4 disks
- create new 4 disks
- attach new disks
- assign those disks to ASM with oracleasm utilty
- create diskgroup archivelog
It worked.
But because I was on AWS and more because it was the ARCHIVELOG diskgroup.
What would I had to do if it was the DATA diskgroup?
Thanks -
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. -
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 ... -
I just tried to resize an ASM disk and although the feedback was 'successful', there doesn't appear to have been any change.
I was attempting to shrink disk DATA_0001 from 200G to 100G. Am I missing something obvious?
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
GROUP_NUMBER NAME PATH OS_MB TOTAL_MB FREE_MB
0 /dev/iscsi/rman11 20489 0 0
0 /dev/iscsi/rmanB11 102398 0 0
0 /dev/iscsi/rman1 20490 0 0
0 /dev/iscsi/vote3 300 0 0
0 /dev/iscsi/vote1 300 0 0
0 /dev/iscsi/rmanP11 204805 0 0
0 /dev/iscsi/vote2 300 0 0
0 /dev/iscsi/rmanP1 204810 0 0
0 /dev/iscsi/rmanB1 102405 0 0
1 DATA_0000 /dev/iscsi/db1 10245 10245 10109
2 FRA_0000 /dev/iscsi/flshbk1 20490 20490 20465
GROUP_NUMBER NAME PATH OS_MB TOTAL_MB FREE_MB
2 FRA_0001 /dev/iscsi/flshbkR1 409605 409605 409262
1 DATA_0001 /dev/iscsi/dbR1 204810 204810 202297
13 rows selected.
SQL> alter diskgroup data resize disk 'data_0001' size 100g;
Diskgroup altered.
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
GROUP_NUMBER NAME PATH OS_MB TOTAL_MB FREE_MB
0 /dev/iscsi/rman11 20489 0 0
0 /dev/iscsi/rmanB11 102398 0 0
0 /dev/iscsi/rman1 20490 0 0
0 /dev/iscsi/vote3 300 0 0
0 /dev/iscsi/vote1 300 0 0
0 /dev/iscsi/rmanP11 204805 0 0
0 /dev/iscsi/vote2 300 0 0
0 /dev/iscsi/rmanP1 204810 0 0
0 /dev/iscsi/rmanB1 102405 0 0
1 DATA_0000 /dev/iscsi/db1 10245 10245 10004
2 FRA_0000 /dev/iscsi/flshbk1 20490 20490 20465
GROUP_NUMBER NAME PATH OS_MB TOTAL_MB FREE_MB
2 FRA_0001 /dev/iscsi/flshbkR1 409605 409605 409262
1 DATA_0001 /dev/iscsi/dbR1 204810 204810 202402
13 rows selected.The free_mb seems to have increased, but otherwise I can't see the effect of my change. Maybe I'm looking in the wrong place??
I tried restarting the ASM instance but it made no difference.
After resizing the disk in ASM I shrunk the disk volume in our storage array. ASM was of course down at the time.
When I attempted to restart ASM I saw this ...
SQL> startup
ASM instance started
Total System Global Area 283930624 bytes
Fixed Size 2158992 bytes
Variable Size 256605808 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15036: disk '/dev/iscsi/dbR1' is truncatedNone of my diskgroups are mounted ...
SQL> select group_number, name, state from v$asm_diskgroup;
GROUP_NUMBER NAME STATE
0 DATA DISMOUNTED
0 FRA DISMOUNTEDHere's the messages from the ASM instance alert log ...
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: cache registered group DATA number=1 incarn=0x5f5e3343
NOTE: cache began mount (not first) of group DATA number=1 incarn=0x5f5e3343
NOTE: cache registered group FRA number=2 incarn=0x5f5e3344
NOTE: cache began mount (not first) of group FRA number=2 incarn=0x5f5e3344
WARNING::ASMLIB library not found. See trace file for details.
NOTE: Assigning number (1,0) to disk (/dev/iscsi/db1)
NOTE: cache dismounting group 1/0x5F5E3343 (DATA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 1/0x5F5E3343 (DATA)
NOTE: cache ending mount (fail) of group DATA number=1 incarn=0x5f5e3343
kfdp_dismount(): 1
kfdp_dismountBg(): 1
NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
ERROR: diskgroup DATA was not mounted
NOTE: Assigning number (2,1) to disk (/dev/iscsi/flshbkR1)
NOTE: Assigning number (2,0) to disk (/dev/iscsi/flshbk1)
NOTE: cache dismounting group 2/0x5F5E3344 (FRA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 2/0x5F5E3344 (FRA)
NOTE: cache ending mount (fail) of group FRA number=2
incarn=0x5f5e3344
kfdp_dismount(): 2
kfdp_dismountBg(): 2
NOTE: De-assigning number (2,0) from disk (/dev/iscsi/flshbk1)
NOTE: De-assigning number (2,1) from disk (/dev/iscsi/flshbkR1)
ERROR: diskgroup FRA was not mounted
ORA-15032: not all alterations performed
ORA-15036: disk '/dev/iscsi/dbR1' is truncated
ERROR: ALTER DISKGROUP ALL MOUNTAny clues?
Thanks,
SteveThanks Markus. I changed the size of the volume back to the original and was able to restart the ASM instances on both nodes. I confirmed it saw the size as the original 200G.
I then shut down ASM on the second node and issued the alter on the first node. Here's what happened ...
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk order by name;
GROUP_NUMBER NAME PATH OS_MB TOTAL_MB FREE_MB
1 DATA_0000 /dev/iscsi/db1 10245 10245 10004
1 DATA_0001 /dev/iscsi/dbR1 204810 204810 202402
2 FRA_0000 /dev/iscsi/flshbk1 20490 20490 20465
2 FRA_0001 /dev/iscsi/flshbkR1 409605 409605 409262
0 /dev/iscsi/rman1 20490 0 0
0 /dev/iscsi/rmanP1 204810 0 0
0 /dev/iscsi/rmanB1 102405 0 0
0 /dev/iscsi/rmanP11 204805 0 0
0 /dev/iscsi/rmanB11 102398 0 0
0 /dev/iscsi/rman11 20489 0 0
10 rows selected.
SQL> alter diskgroup data resize disk 'data_0001' size 100g;
alter diskgroup data resize disk 'data_0001' size 100g
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15066: offlining disk "DATA_0001" may result in a data lossHere's the details from the alert log ...
SQL> alter diskgroup data resize disk 'data_0001' size 100g
NOTE: requesting all-instance membership refresh for group=1
WARNING: cache read a corrupted block gn=1 dsk=1 blk=257 from disk 1
NOTE: a corrupted block was dumped to /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
ERROR: cache failed to read gn=1 dsk=1 blk=257 from disk(s): 1
ORA-15196: invalid ASM block header [kfc.c:9133] [endian_kfbh] [2147483649] [257] [0 != 1]
System State dumped to trace file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
NOTE: cache initiating offline of disk 1 group 1
WARNING: initiating offline of disk 1.3688884620 (DATA_0001) with mask 0x7e
NOTE: initiating PST update: grp = 1, dsk = 1, mode = 0x15
kfdp_updateDsk(): 14
Thu May 07 15:45:38 2009
kfdp_updateDskBg(): 14
ERROR: too many offline disks in PST (grp 1)
Thu May 07 15:45:38 2009
NOTE: halting all I/Os to diskgroup DATA
Thu May 07 15:45:38 2009
SQL> alter diskgroup DATA dismount force
NOTE: active pin found: 0x0x6ddf6060
NOTE: active pin found: 0x0x6ddf6168
ERROR: ORA-15130 signalled during resize of diskgroup DATA
Thu May 07 15:45:38 2009
NOTE: membership refresh pending for group 1/0xdc0f1999 (DATA)
kfdp_query(): 15
kfdp_queryBg(): 15
SUCCESS: refreshed membership for 1/0xdc0f1999 (DATA)
ERROR: ORA-15130 thrown in RBAL for group number 1
Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
ORA-15130: diskgroup "DATA" is being dismounted
Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15066: offlining disk "DATA_0001" may result in a data loss
ERROR: alter diskgroup data resize disk 'data_0001' size 100g
NOTE: cache dismounting group 1/0xDC0F1999 (DATA)
NOTE: dbwr not being msg'd to dismount
Thu May 07 15:45:41 2009
Dirty detach reconfiguration started (old inc 6, new inc 6)
List of nodes:
0
Global Resource Directory partially frozen for dirty detach
* dirty detach - domain 1 invalid = TRUE
10 GCS resources traversed, 0 cancelled
Dirty Detach Reconfiguration complete
Thu May 07 15:45:41 2009
freeing rdom 1
Thu May 07 15:45:41 2009
WARNING: dirty detached from domain 1
NOTE: cache dismounted group 1/0xDC0F1999 (DATA)
kfdp_dismount(): 16
kfdp_dismountBg(): 16
NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
NOTE: De-assigning number (1,1) from disk (/dev/iscsi/dbR1)
SUCCESS: diskgroup DATA was dismounted
SUCCESS: alter diskgroup DATA dismount force
ERROR: PST-initiated MANDATORY DISMOUNT of group DATA
Thu May 07 15:46:06 2009
SQL> alter diskgroup data resize disk 'data_0001' size 100g
ORA-15032: not all alterations performed
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ERROR: alter diskgroup data resize disk 'data_0001' size 100gLooks like my earlier attempt has indeed screwed up something so even though the instances start OK and mount the diskgroup, I think there's a fair chance something would go splat sooner rather than later.
As this is a test database, I think I'll cut my losses and rebuild the diskgroup then restore it from backup. I'm assuming the effort involved in correcting the corruption will be greater than rebuilding and restoring.
Do you agree with this?
Then I'll try again and hopefully get it right.
Thanks for your help!!!
Steve -
Hi,
I am consistently getting the following error since yesterday while mounting the ASM disk.
1. I created the ASM disks successfully and created the appropriate ASM DiskGroups using asmca utility.
2. I was able to see the diskgroups as mounted from asmcmd tool.
3. All of a sudden, all the diskgroups were dismounted yesterday and I see the following error in the alert logs for all the
diskgroups.
4. This is using ASM11g
As I exhausted all my avenues to fix, I have turned to you for further assistance. Please do the needful.
SQL> /* ASMCMD */ALTER DISKGROUP DataVSPSI MOUNT
NOTE: cache registered group DATAVSPSI number=3 incarn=0x7934bf5d
NOTE: cache began mount (first) of group DATAVSPSI number=3 incarn=0x7934bf5d
NOTE: Assigning number (3,0) to disk (ORCL:D01_VSP_SI)
Thu Dec 27 17:38:29 2012
NOTE: start heartbeating (grp 3)
kfdp_query(DATAVSPSI): 11
kfdp_queryBg(): 11
NOTE: cache opening disk 0 of grp 3: D01_VSP_SI label:D01_VSP_SI
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache mounting (first) external redundancy group 3/0x7934BF5D (DATAVSPSI)
NOTE: starting recovery of thread=1 ckpt=2.1 group=3 (DATAVSPSI)
WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
AU:4 disk_offset(bytes):4333568 io_size:122880 operation:Read type:asynchronous
result:I/O error process_id:32162
WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
AU:4 disk_offset(bytes):4202496 io_size:131072 operation:Read type:asynchronous
result:I/O error process_id:32162
ORA-15080: synchronous I/O operation to a disk failed
ERROR: ASM recovery failed to read ACD
NOTE: cache initiating offline of disk 0 group DATAVSPSI
NOTE: process 32162 initiating offline of disk 0.3940831150 (D01_VSP_SI) with mask 0x7e in group 3
WARNING: Disk D01_VSP_SI in mode 0x7f is now being taken offline
NOTE: initiating PST update: grp = 3, dsk = 0/0xeae44fae, mode = 0x15
kfdp_updateDsk(): 12
kfdp_updateDskBg(): 12
ERROR: too many offline disks in PST (grp 3)
WARNING: Disk D01_VSP_SI in mode 0x7f offline aborted
Thu Dec 27 17:38:29 2012
NOTE: halting all I/Os to diskgroup DATAVSPSI
NOTE: crash recovery signalled OER-15130
ERROR: ORA-15130 signalled during mount of diskgroup DATAVSPSI
NOTE: cache dismounting (clean) group 3/0x7934BF5D (DATAVSPSI)
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 3/0x7934BF5D (DATAVSPSI)
Also, I think the lower level disk is fine as I am able to write to the disk as follows :
[oracle@rmanqa01 trace]$ dd of=/dev/sdp1
Test Test
0+1 records in
0+1 records out
10 bytes (10 B) copied, 4.97435 seconds, 0.0 kB/s
[oracle@rmanqa01 trace]$ id
uid=500(oracle) gid=500(oinstall) groups=6(disk),500(oinstall),501(dba),502(oper),503(asmadmin),504(asmdba),505(asmoper),506(horcm)
[oracle@rmanqa01 trace]$ ls -l /dev/sdp1
brw-rw---- 1 root disk 8, 241 Dec 28 11:59 /dev/sdp1
[oracle@rmanqa01 trace]$
The oracleasm also lists the disk D01_VSP_SI as follows :
[root@rmanqa01 log]# /etc/init.d/oracleasm listdisks
A01_VSP_SI
ADSK01
ARCH_AMS_SI
D01_VSP_SI
DATA_AMS_SI
DDSK01
DEMO_ARCH
DEMO_DATA
L01_VSP_SI
RDSK01
REDO_AMS_SI
You have new mail in /var/spool/mail/root
[root@rmanqa01 log]# /etc/init.d/oracleasm querydisk D01_VSP_SI
Disk "D01_VSP_SI" is a valid ASM disk
[root@rmanqa01 log]#
kfed tool was giving proper data till yesterday.
Today, I am getting the following :
./kfed read /dev/oracleasm/disks/D01_VSP_SI
kfbh.endian: 84 ; 0x000: 0x54
kfbh.hard: 101 ; 0x001: 0x65
kfbh.type: 115 ; 0x002: *** Unknown Enum ***
kfbh.datfmt: 116 ; 0x003: 0x74
kfbh.block.blk: 1936020512 ; 0x004: T=0 NUMB=0x73655420
kfbh.block.obj: 2147486324 ; 0x008: TYPE=0x8 NUMB=0xa74
kfbh.check: 2886846267 ; 0x00c: 0xac11c73b
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
ERROR!!!, failed to get the oracore error message
[oracle@rmanqa01 bin]$
Please help.
Thanks
V V
Edited by: user13479556 on Dec 28, 2012 12:00 PMThanks Berx for pointing that out.
I deleted the ASM disks and the diskgroups and re-created a fresh and was able to start the ASM instance and mount the DGs.
Now the mount is persistent, but the dbca fails with the following error in the alert log. Under what situations can this error be seen ?
NOTE: Loaded library: System
SUCCESS: diskgroup DATAAMSSI was mounted
SUCCESS: diskgroup ARCHAMSSI was mounted
ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.DATAAMSSI.dg*ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.ARCHAMSSI.dg*Mon Dec 31 20:25:25 2012
SUCCESS: diskgroup LOGAMSSI was mounted
Mon Dec 31 20:25:25 2012
ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.LOGAMSSI.dg
Mon Dec 31 20:25:25 2012
Successful mount of redo thread 1, with mount id 784925673
Completed: Create controlfile reuse set database "R3AMSSI"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'+DATAAMSSI/R3AMSSI/system01.dbf',
'+DATAAMSSI/R3AMSSI/sysaux01.dbf',
'+DATAAMSSI/R3AMSSI/undotbs01.dbf',
'+DATAAMSSI/R3AMSSI/users01.dbf'
LOGFILE GROUP 1 ('+LOGAMSSI/R3AMSSI/redo01.log') SIZE 51200K,
GROUP 2 ('+LOGAMSSI/R3AMSSI/redo02.log') SIZE 51200K,
GROUP 3 ('+LOGAMSSI/R3AMSSI/redo03.log') SIZE 51200K RESETLOGS
Stopping background process MMNL
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
Mon Dec 31 20:25:28 2012
MMON started with pid=17, OS id=10452
ALTER SYSTEM enable restricted session;
Mon Dec 31 20:25:28 2012
MMNL started with pid=18, OS id=10454
alter database "R3AMSSI" open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 945183
Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
Mon Dec 31 20:25:29 2012
Checker run found 5 new persistent data failures
Mon Dec 31 20:27:07 2012
I can verify from asmcmd that the redologs mentioned above as missing is very much present in '+LOGAMSSI/R3AMSSI'
Thanks
V V -
Hi I am using Oracle 10gR2 on Solaris 10. I have some 12 ASM disks in a Disk Group. I want to remove 3 ASM Disks. Can I do this operation online? Will my data be affected? How should I proceed about it? When I will remove the ASM Disks, can I safely detach those disks physically? please help.
regardsahsen.javaid wrote:
Hi I am using Oracle 10gR2 on Solaris 10. I have some 12 ASM disks in a Disk Group. I want to remove 3 ASM Disks. Can I do this operation online? As already commented, yes. I would like to give you a practical example of how utterly neat ASM is in this regard and why it is IMO a major mistake not to use ASM.
We had to swap storage systems. This means that we have to migrate an entire Oracle database (over 1TB in size) from one set of LUNs to a completely different set of LUNs (on a different storage system).
The new LUNs are added to the existing diskgroup. The old LUNs are dropped (the drop is of course not immediate). A rebalance is issued. The next morning the entire database has been moved and restriped on the new set of LUNs and the old LUNs can now be removed from the system. This while the database was up and running and normal processing continued uninterrupted (this is a 24x7 database).
Then I get comments from some customers (like from a major local financial institution recently) that "+No, we do not want to use ASM as we rather use Veritas+". People like that are missing the point of what ASM is. Totally. -
Startup of Clusterware with missing voting disk
Hello,
in our environment we have a 2 node cluster.
The 2 nodes and 2 SAN storages are in different rooms.
Voting files for Clusterware are in ASM.
Additionally we have a third voting disk on a NFS server (configured like in this descripton: http://www.oracle.com/technetwork/products/clusterware/overview/grid-infra-thirdvoteonnfs-131158.pdf&ei=lzJXUPvJMsn-4QTJ8YDoDg&usg=AFQjCNGxaRWhwfTehOml-KgGGeRkl4yOGw)
The Quorum flag is on the disk that is on NFS.
The diskgroup is with normal redundancy.
Clusterware keeps running when one of the VDs gets lost (e.g. storage failure).
So far so good.
But when I have to restart Clusterware (e.g. reboot of a node) while the VD is still missing, then clusterware does not come up.
Did not find an indication if this whether is planned behaviour of Clusterware or maybe because I missed a detail.
From my point of view it should work to start Clusterware as long as the majority of VDs are available.
Thanks.Hi,
actually what you see is expected (especially in a stretched cluster environment, with 2 failgroups and 1 quorum failgroup).
It has to do with how ASM handles a disk failure and is doing the mirriong (and the strange "issue" that you need a third failgroup for the votedisks).
So before looking at this special case, lets look at how ASM normally treats a diskgroup:
A diskgroup can only be mounted in normal mode, if all disks of the diskgroup are online. If a disks is missing ASM will not allow you to "normally" mount the diskgroup, before the error situation is solved. If a disks is lost, which contents can be mirrored to other disks, then ASM will be able to restore full redundancy and will allow you to mount the diskgroup. If this is not the case ASM expects the user to tell what it should do => The administrator can issue a "alter diskgroup mount force" to tell ASM even though it cannot held up the required redundancy it should mount with disks missing. This then will allow the administrator to correct the error (or replaced failed disks/failgroups). While ASM had the diskgroup mounted the loss of a failgroup will not result in a dismount of the diskgroup.
The same holds true with the diskgroup containing the voting disks. So what you see (will continue to run, but cannot restart) is pretty much the same like for a normal diskgroup: If a disk is lost, and the contents does not get relocated (like if the quorum failgroup fails it will not allow you to relocatore, since there are no more failgroups to relocate the third vote to), it will continue to run, but it will not be able to automatically remount the diskgroup in normal mode if a disk fails.
To bring the cluster back online, manual intervention is required: Start the cluster in exclusive mode:
crsctl start crs -exclThen connect to ASM and do a
alter disgkroup <dgname> mount forceThen resolve the error (like adding another disk to another failgroup, that the data can be remirrored and the disk can be dropped.
After that a normal startup will be possible again.
Regards
Sebastian -
ASM disk shows different Readings
Our env is 3 node rac with ASM and 6 Standby Databases on it.
I am Missing around 1.5 TB for FRA disk on ASM
ASM disk FRA shows :
ASMCMD> du FRA/
Used_MB Mirror_used_MB
240646 240646
Standby database shows the usage of ASM Disk Group and it says 3 % is left on FRA
SQL> SELECT name, free_mb, total_mb, free_mb/total_mb*100 as percentage FROM v$asm_diskgroup;
NAME FREE_MB TOTAL_MB PERCENTAGE
DATA 1741308 2047972 85.0259672
FRA 76433 2047972 3.7321311
FUNDATA 1023841 1023986 99.9858397
FUNFRA 958964 1023986 93.6501085
OCR 1631 2038 80.0294406
VOTE 2550 3057 83.4151129
Can anyone Guide me on this please.Hi,
Check the redundancy of your disk groups Doc: ORACLE-BASE - Automatic Storage Management (ASM) in Oracle Database 10g
NORMAL REDUNDANCY - Two-way mirroring, requiring two failure groups.
HIGH REDUNDANCY - Three-way mirroring, requiring three failure groups.
EXTERNAL REDUNDANCY - No mirroring for disks that are already protected using hardware mirroring or RAID. If you have hardware RAID it should be used in preference to ASM redundancy, so this will be the standard option for most installations
HTH -
Oracle ASM Disk Name Lenght Limit
Hi,
Does anyone know wheter or not oracleasm has a maximum disk name lenght limit, I have a situation where "#oracleasm listdisks" shows the same name for 5 of my disks and seems to have truncated the last character from the disk name.
So, now my ASM Diskgroup is not starting up because it sees that there are "missing" disks, but they are not missing, they are just listed with the same Disk Name.
Commands used to create the disks:
oracleasm createdisk RAC_DATA146_500GB_DISK001 /dev/emcpowerek1
oracleasm createdisk RAC_DATA146_500GB_DISK002 /dev/emcpowerem1
oracleasm createdisk RAC_DATA146_500GB_DISK003 /dev/emcpowerej1
oracleasm createdisk RAC_DATA146_500GB_DISK004 /dev/emcpowerel1
oracleasm createdisk RAC_DATA146_500GB_DISK005 /dev/emcpowerei1
Now, see the output when I do a querydisk:
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerek1
Disk "/dev/emcpowerek1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerem1
Disk "/dev/emcpowerem1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerej1
Disk "/dev/emcpowerej1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerel1
Disk "/dev/emcpowerel1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerei1
Disk "/dev/emcpowerei1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
So, it looks like the version of oracleasm that I'm running has a name lenght limit? IS this possible?
[root@birac01 ~]# rpm -qa | grep oracleasm
oracleasm-support-2.0.3-1
oracleasm-2.6.9-55.ELsmp-2.0.3-1
oracleasmlib-2.0.2-1
Can anyone please help?
Regards
Stephan
Edited by: user1675141 on Mar 22, 2011 2:10 AMOracleasmlib does not seem to advertise such information. As such it might be a poor design that it is not verifiying user input.
According to http://download.oracle.com/docs/cd/E11882_01/install.112/e17212/storage.htm#CWLIN294
+"The disk names that you specify can contain uppercase letters, numbers, and the underscore character. They must start with an uppercase letter."+
The Oracle ASM assistant documentation shows:
+"A volume name of Oracle ASM can be a maximum of 11 alphanumeric characters; dashes are not allowed. The first character must be alphabetic"+
Why are you using such long volume and device names in first place? I would abbreviate the names and make them shorter. The url above will also show you information about configuring multipath and udev.
You could try to query device names using:
/etc/init.d/oracleasm querydisk -p VOL1
and rename volumes using:
/etc/init.d/oracleasm renamedisk /dev/sdb1 VOL1
Edited by: Dude on Mar 22, 2011 5:19 AM -
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
Maybe you are looking for
-
How to change default zoom in outlook 365 permenently
I use the preview/reading pane in outlook 365 and I can see the slider bar at the bottom where I can adjust the zoom. Problem is I have to enlarge it each time for every email I want to read. How can set this to something other than 100% and make it
-
can I load my old fonts somehow?
-
Media core - what is it all about?
Anyone explain the difference between 'Common/Mediacore' and 'Premiere/Plugins' folders or the reason behind 'Mediacore'? Why are plugins stored in either of these? Appears to me that a plugin stored in Mediacore is available to AEFX and Premiere. If
-
NEED HELP OPENING SAVED ADOBE FILE
I had some important info saved on a disc (an adobe reader file). I hadn't tried opening it in a while but when I try opening it it says something about a file i/o error. Is there a solution or is the info lost? I don't know if it has anything to
-
Why is my computer making a high-pitched noise?
It sounds like a plane taking off. It is not the case...