Removal of ASM Disks

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.
regards

ahsen.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.

Similar Messages

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.
regards

If 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.

Correct steps to reload ASM disks into a running ASM instance on Linux RHEL

Hi guys,
i hope this is the correct forum, awfully i did not found any document specifically talking abou this.
first of all let me explain quickly my goal: in my server (it contains the same data of 3 production RACs for reporting purposes) i would like to shutdown a single instance (i have 3) and realod his disks to refresh the data or because for some reason its mount into ASM is failed.
this is a mix of Oracle ASM and Linux stuff...
on this server there is a shell script that perform the following steps:
1) shutdown 3 instances of 11g (11.2.0.2.0 with patch for asm already installed for bug... dont remember)
2) shutdown ASM instance
3) stop ASMLIB
4) stop multipathd
5) remove all disks devices from linux
6) take a snapshot on the 3 production RACs
7) remap the disks to this server (SAN stuff)
8) rescan the disks
9) start ASMLIB
10) start ASM instance
11) mount the DiskGroups
12) start 3 oracle instances
this works fine... my problem is when i try to refresh the disks of just 1 of the 3 instances, i perform the following steps:
1) stop instance ABC
2) dismount ABC diskgroups related to ABC instance
3) wait 5 seconds (dont ask... if idid it without ASM still have the disks locked)
4) delete the ASMLIB disks (oracleasm deletedisk XYZ) relate to such diskgroups
5) remove mpaths related to the disks that need to be refreshed or correctly mounted oneagain
6) remove devices
7) unmap disks on SAN
8) take snapshot (clone disks)
9) map disks from SAN
10) delete bindings file
11) rescan devices
12) execute multipath command (to rebuild bindings file)
13) execute oracleasm scandisks
14) mount DiskGroups
15) start instance ABC
actually i dont understand why the OS (or specifically ASMLIB) do not recognize me anymore one of the ASMLIB disk
do you have any idea ? or im completly crazy doing that ?
best regards,
Luca

Hi,
well this step
4) delete the ASMLIB disks (oracleasm deletedisk XYZ) relate to such diskgroups
is not good. Because it will clear the ASM Header and as a result ASM will never again be able to detect the disks.
So it is clear that "scnadisks" later will not see the disks, because you wiped them.
Worse: You did the snapshot after deleting them... this gets tricky to get them "repaired" again.
However there is the possibility to relabel a dropped ASM disks. You need to open an SR for this, since the procedure to restore the lost ASM header is not that simple..
Regards
Sebastian

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.

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 PM

As 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

ASM Disk Migration

HI There,
Im working on an 11.2.0.3 GI and RDBMS running on AIX 7.1
I have a situation where one of the one of the ASM disk groups on a particular cluster consists of 20 disks, 10 of which need to be swapped out for 10 new disks.
As far as I am aware (correct me if im wrong) the following procedure should work, can be done online and should have no impact to any databases using the diskgroup (apart from the asm rebalance):
-Start with 20 disks (lets call them 'disk1 to disk20' allocated to diskgroup '+DISKGROUP_A'
- I have ten new disks (lets call them disk21 - disk30'
- I want to swap out 'disk11 to 'disk20' for new disks 'disk21 to disk30'
- First Add disks 'disk21 to disk30' to ASM diskgroup '+DISKGROUP_A'
- Allow rebalance to finish
- Once rebalance finished drop 'disk11 to disk20' from '+DISKGROUP_A'
- Allow rebalance to finish again
- Confirm that disks 'disk11 to disk20' are now shown as 'FORMER'
- Disks can then physically be removed.
My Question, is there a better way of doing what I am trying to achieve here, the above process worries me a little, simply because Im putting my self totally in the hands of oracle, crossing my fingers and hoping it works.
- Any better suggestions?
- Any suggestions around safeguarding the above approach?
Any opinions would be appreciated
Thanks

Hi
The best way is to allow the ASM to do the migration:
Create the new ASM disks
Add those disks to your ASM diskgroup
Wait to the re balance processes finish
Remove old disks from your diskgroup
Wait to the re balance processes finish
Drop the old ASM disks
Disconnect physical disks
I migrate all the storage (old SAN to new SAN ) for one RAC including OCR_Voting with zero down time, without problems.
This is the post:
OCR_Voting Disk Migration
Regards

ASM Disk offline - State hung

Hey in my ASM configuration I setup this
Disk Path ASM Name Failure Group
/dev/raw/raw4 Data1 FG1_Data [on SAN1]
/dev/raw/raw5 Data2 FG2_Data [on SAN2]
/dev/raw/raw6 Reco1 FG1_Reco [on SAN1]
/dev/raw/raw7 Reco2 FG2_Reco [on SAN2]
all good.
My I switched off SAN1. A query on v$asm_disk shows disk DATA1 & RECO1 as offline - hung state.
I did in the asm instance in sqlplus:
ALTER DISKGROUP DATA DROP DISK data1; -> success
ALTER DISKGROUP RECO DROP DISK reco1; -> success
ALTER DISKGROUP DATA ADD failgroup DATA3 '/dev/raw/raw4'; -> success
ALTER DISKGROUP RECO ADD failgroup RECO3 '/dev/raw/raw6'; -> success
The query on v$asm_disk stills show the DATA1 and RECO1 - but DATA3 and RECO3 as well.
Is it right, that the "old" entries will disappear, once the ASM instance is restarted ? I can´t do this at the moment.
In generell - why went the ASM disks to offline ?
SAN1 was switched off for about 5 minutes - and was then switched back on.
Is this expected behaviour ?

Hi Chris,
as long as the information is still partially valid, the devices will be displayed in v$asm_disk. Main reason is: Some Oracle processes still have handles open on these devices, and as long as they exist the devices can still be seen.
A Restart of ASM + database will definitely remove these entries (if they cannot be seen by the operating system).
Regarding your other question: Oracle can only detect if a device is going offline (errors in the database and asm alter log). If a device goes online again, Oracle does not check this (this would be a major overhead to rescan lets say every minute to see if a disk is back online).
Hence you have to reinclude the dropped/offlined disks yourself.
Depending on the version (10g or 11g) and depending on the diskgroup compatibility level for rdbms a disk can simply be returned into the diskgroup (11g - alter diskgroup <dg> set disk <disk> online) and resilvered or have to be reincluded into the ASM instance (no resilvering, but a complete rebalance 10g: alter diskgroup <dg> add disk <disk> to failgroup <fg> [force])
Sebastian

Why I can't drop ASM disks and stop ASMLib ?

Hi, I wanted to delete disks but this operation failed:
1.
/etc/init.d/oracleasm deletedisk DATA1
Removing ASM disk "DATA1" [FAILED]
I know there is solution to overwrite ASM header information on a disk
dd if=/dev/zero of=<your_raw_device> bs=1024 count=100
and then droping is successful
but I also saw resources that said it should be count=50
Could anyone confirm count=100 or 50 ?
2.
Besides of that I tried to stop ASMLib and it failed too:
/etc/init.d/oracleasm stop
Dropping Oracle ASMLib disks: [ OK ]
Shutting down the Oracle ASMLib driver: [FAILED]
Ok, so using dd will help me to get rid of disks, but I worry about ASMLib in general, why I can't stop it? All ASM instances were removed before. There is no ASM software installed, besides ASMLib.

The story is like that:
During Grid Infrastructure 11.2 installation I wanted to create new disk group but all available disks ware marked as 'MEMBER', so that I couldn't use any of them. Then I investigated that there is no database using ASM, and no ASM software installed. But ASMLib lists some disks. So former diskgroups must have been dropped in a bad way. As disks are marked as 'MEMBER' I wanted to drop them and create new ones. But this operation failed.
Yes, I use root account
oracleasm exit failed too:
oracleasm exit
Unmounting ASMlib driver filesystem: failed
Unable to unmount ASMlib driver filesystem
/var/log/oracleasm :
Cleaning any stale ASM disks...
Unmounting ASMlib driver filesystem: umount: /dev/oracleasm: device is busy
umount: /dev/oracleasm: device is busy
failed
Unable to unmount ASMlib driver filesystem
How to deal with this problem? Please help.
Edited by: Przemek P on 2012-02-07 07:00

OUI will not detect ASM disks on EqualLogic PS6100

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

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

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 in

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

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,
DB

user564706 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 Dalavai

Looks 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.
--MM

hi
use the following linux command as root:
$oracleasm listdisks
hth

Removal of ASM Disks

Similar Messages

Maybe you are looking for