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.

Similar Messages

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

Question on Asm Disk Groups

Hello,
I have five 200gb (Total 1 TB) disks on my prod rac environment and we are using 11g 11.1.0.6. These disks have been mounted a while back and the db is currently 50gb full.
My question is i need to unmount one of the disks of 200gb since we are having a shortage of disks at the moment, so i can use it as the flash recovery drive. My understanding with asm is that even if once disk fails the rebalnce act would happen and it would stripe data across four disks without any loss of data or downtime.
We are using external redudancy on these disks and they use Raid 5.
Can i attempt this, if this is possible could you guys give me the best command i can use to do this.
Thx All

Just do an
alter diskgroup <name> drop disk <name>;The documentation states:
DROP DISK The DROP DISK clause lets you drop one or more disks from the disk group and automatically rebalance the disk group. When you drop a disk, Automatic Storage Management relocates all the data from the disk and clears the disk header so that it no longer is part of the disk group.
Note:
If you need to drop more than one disk i strongly recommend to do it in a single step, e.g.
alter diskgroup <name> drop disk <nameA>,<nameB>;Thsi will do the rebalance only once.
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

ASM disk corrupted

Hi,
A few days ago, I have asked a question about“ASM disk header corruption”at ASM disk header corruption .
Because it was only my assumption, I didn't think about it deeply. This morning I encountered a problem from a thread. It said that the diskgroup couldn't mount, and ORA-15196 appeared in the alert.log.
It occurred to me that if the diskgroup couldn't mount and the header of an asm disk corrupted, how should I deal with it? Will the data in the ASM disk be lost?
Please help me with this problem.
Thanks in advance.

user526904 wrote:
I hope you have the backup, Incase its the media failure and if you can detemine the corroupt datafiles, just restore the corroupt datafiles from backup and recover them. Database backups cannot restore a corrupted ASM header. rman backups the Oracle data files. Not the physical ASM disk itself with the disk's headers.
To restore that, you will need a physical disk backup. A physical disk backup will need all processes using the disks to terminate in order to ensure that all file handles are closed and that the backup is consistent. Not something that is easily done in today's 24x7 environments. RAID is usually used to address this type of failure (e.g. via hot swappable disks, where you simply replace the faulty disk with a new one, while the storage system is running).
So where you do not have that physical redundancy, and have to deal with "physical disk" error (like corrupted header blocks), you need to be extremely careful on how to try and recover that. I would not even try and touch that disk. I will ensure that no processes touch that disk at all, create a duplicate disk (same size) and manually "mirror" the data (using dd for example). This will serve two purposes. Tests whether physical reads on the problem disk succeeds (is this actual media failure, or logical failure?). And create a 2nd disk that can be used for testing/playing purposes, prior to trying any fixes on the problem disk.

ORA-15020: discovered duplicate ASM disk

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

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

Cloning ASM disks question?

I have a customer who has been running oracle 10.2.0.4 two node rac on HPUX Itanium platform and using raw devices for the datafile locations. They use EMC clraion for the storage platfom.
The customer uses EMC snapshot/cloning technology on the storage side to create a clone of the database luns for their staging database environment. This works well and they are able to simply snap the luns on the storage side and then simply mount them on another host and bring the database copy up an another host.
Well, now that they are in the process of 11g upgrade and the fact that raw devices will no longer be supported going forward for the most part the cusomter would like to start to use ASM for the clustered file system for the RAC databases.
I am trying to find out if there are any white papers or some documentation on how we could make clones when the disks are ASM disks? I know that EMC can snapshot the luns as they have in the past but not sure how we can get them mounted up in another ASM instance on a separate server?
Just wanting to know if anyone has some experience on cloning ASM disk or disk groups between different hosts and maybe some supporting documentation to go along with it.
Thanks.

YOU CAN. You can use the same EMC copy for the ASM Lun, attach it to another server and can start the ASM instance up. It is quiet same as you were doing it with raw devices.
ASM files has ASM headers on it. When you copy the disks over, asm instance can recognize those headers and be able to come online. ASm instance can identify the copied disks from their disk headers.

Oracle ASM Disks Question

Hi,
We have two Linux hosts accessing EMC SAN LUNs and we have Oracle ASM Disks created on those devices. Both the Linux Hosts (server1/2)are in once Dell Blade Chassis1 and one of the Server we are planning to move to a different Dell Chassis(2) to have redundency in case of Chassis1 faliure. But if we move one server2 to Chassis2 the HBA WWN Number for the host on the new Dell Chassis2 will change ( WWNs are assigned by Chassis on Dell) and the server2 will loose all the SAN LUNs from EMC Array. I will have to rezone the new server WWNs to storage and pesent the same disks again and rescan the disks which will take couple of reboots. During this period EMC LUNs will not be visible to server2 and I would like to what will happen to ASM disks on the server2 and how to I accomlish this goal? Any detailed steps please? This is a production system with oracle 11g running.
This is the output of emc powerpath devices (LUNs) which is same on both the hosts.
[root@server2 ~]# powermt display dev=all | grep emc
Pseudo name=emcpowerl
Pseudo name=emcpowerj
Pseudo name=emcpowerf
Pseudo name=emcpowerk
Pseudo name=emcpowerg
Pseudo name=emcpowerh
Pseudo name=emcpowerm
Pseudo name=emcpoweri
[root@server2 ~]#
This are the ASM disks on both the hosts:
[root@server2 ~]# oracleasm listdisks
DATA01_F1
DATA01_G1
DATA01_H1
DATA01_I1
FRA01_L1
LOG01_J1
LOG01_K1
[root@server2 ~]#
Thanks in advance.

808306 wrote:
But if we move one server2 to Chassis2 the HBA WWN Number for the host on the new Dell Chassis2 will change ( WWNs are assigned by Chassis on Dell) and the server2 will loose all the SAN LUNs from EMC Array.This does not sound correct to me. WWNs are global - not local. If the WWN is foo123 on server1 for EMC LUN1, why would it not also be foo123 on server2 for EMC LUN1? When you move to server3 or install server3, why would EMC LUN1 not have a WWN of foo123 on server3?
I will have to rezone the new server WWNs to storage and pesent the same disks again and rescan the disks which will take couple of reboots. Using Powerpath perhaps - using multipath, not. New devices (LUNs) can be made visible by the kernel my refreshing multipath - no reboot required. If existing LUNs are going to be changed - yes, a single reboot will be needed. But not multiple (unless you have a driver issue with stale connections not being reset on the storage server side).
This is the output of emc powerpath devices (LUNs) which is same on both the hosts.We dropped Powerpath a long time ago. There were compatibility issues between it and AsmLib kernel drivers. Powerpath taints the Linux kernel and limits kernel upgrade flexibility. I refuse to run it on our new clusters. I use multipath instead - the very same s/w used by some of the largest clusters (with Pentabyte storage) in the world. The comfort factor using Open Source drivers (and certified for that kernel version) is significantly higher than installing 3rd party kernel driver binaries - and having to deal with a 2nd party when it comes to o/s and kernel support.

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.

Looking for information on the below questions on ASM

Scenario: (Oracle 10g on Windows 2003 with EMC storage)
ASM Partition table crashed for LUN 20 on 18th July
DB was up and running till 23rd July (New LUN (LUN 36) was presented and the RMAN backup used to restore the data that were residing on the corrupt LUN)
End of the day everything screwed up and the complete grid (4 nodes) was rebuild.
Links:
As mentioned in the link: http://www.exforsys.com/forum/oracle-database/487-what-asm-instance-oracle.html
"The ASM instance is only involved during the creation or deletion of files and when disk configurations change (such as dropping or adding a disk). When these types
of changes occur, the ASM instance automatically rebalanced the disks and provides the necessary information to refresh the extent map in the SGA of the database
instance. Of course, this process requires that the ASM instance run concurrently with the database instance, and only shut down after the database instance is
closed."
As mentioned in the link: http://www.orafaq.com/wiki/ASM_FAQ#ASM_disk_header.2Fsuperblock_backups.3F
"ASM disk headers (super-blocks) cannot be backed up and restored in Oracle 10g. By implication, if you use EXTERNAL REDUNDANCY and a single disk's header is
accidentally overwritten, the entire disk group will have to be restored."
As mentioned in the link: http://www.datadisk.co.uk/html_docs/oracle/asm.htm
"ASM is a special instance that does not have any data files, there is only ASM instance one per server which manages all ASM files for each database. The instance
looks after the disk groups and allows access to the ASM files. Databases access the files directly but uses the ASM instance to locate them. If the ASM instance is
shutdown then the database will either be automatically shutdown or crash. "
With the above scenario and the documents provided in the links above, I am unable to get the complete picture of what went wrong. Will be great if some one could
through more light on the below questions. (Note: we have multiple vendor engaged managing different part of this outage and unable to get the real fact of what went
wrong)
1, The ASM had given the details of the disk to the DB, and the DB is managing the disk directly. Also the DB and the ASM instance were up and running till 23rd is
what i understand going by the details given in the above links, in this scenario how can we confirm that the partition table is corrupt / missing. Is their a way to
check the same?
2, ASM disk headers (super-blocks) cannot be backed up, that means that it can not be read directly. Then is it possible to say that the ASM disk header is corrupt /
missing?
3, If the ASM disk header / partition table of LUN 20 is corrupt on 18th, can the DB run till 23rd without any issue? will the ASM & DB does not crash?
4, ASM will strip the data across the available LUN's, will it not be able to rebuild the data on the newly presented LUN 36 instead of using RMAN backup to rebuild the
data? or is the ASM not configured as it should be done. (WE have multiple LUN's presented to this Grid)
Edited by: 880333 on Aug 19, 2011 12:35 AM

What relation with the Oracle Forms product ?
Francois

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

Creation of ASM disk for OUI

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.

Problem with create asm disk group

Hi all
I am about configuring ASM, so I have downloaded the Grid infrastructure 11g (32 bit), I have configured and created parameters and directories.
I runned the installer but get stack at the 3 step where I have to change the discovery path. I have taped as path /dev where I have created 3 partitions sdb1, sdc1 and sdd1.
Is there any thing should I perform on partitions may be or parameters to set before I go through the installation?
Thanks for help

You can use the below link to install ASMLIB:
http://gssdba.wordpress.com/category/asm/
REFERANCE : Doc ID 580153.1
There are two different methods to configure ASM on Linux:
ASM with ASMLib I/O: This method creates all Oracle database files on raw block devices managed by ASM using ASMLib calls. RAW devices are not required with this method as ASMLib works with block devices.
ASM with Standard Linux I/O: This method creates all Oracle database files on raw character devices managed by ASM using standard Linux I/O system calls. You will be required to create RAW devices for all disk partitions used by ASM.
You can download the ASMLIB rpm’s from below URL:
http://www.oracle.com/technetwork/server-storage/linux/downloads/rhel5-084877.html
STEP 01: LOG IN AS ROOT USER AND INSTALL THE RPMS
[root@node1 ASMLIB]# rpm -Uvh oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm \
> oracleasmlib-2.0.4-1.el5.i386.rpm \
> oracleasm-support-2.1.8-1.el5.i386.rpm
warning: oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing… ########################################### [100%]
1:oracleasm-support ########################################### [ 33%]
2:oracleasm-2.6.18-164.el########################################### [ 67%]
3:oracleasmlib ########################################### [100%]
STEP 02: CONFIGURE ASMLIB
[root@node1 ASMLIB]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets (‘[]‘). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
STEP 03 :CREATE ASM DISK
[root@node1 ASMLIB]# /etc/init.d/oracleasm listdisks
[root@node1 ASMLIB]#
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL1 /dev/sdb1
Marking disk “VOL1″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL2 /dev/sdc1
Marking disk “VOL2″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL3 /dev/sdd1
Marking disk “VOL3″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL4 /dev/sde1
Marking disk “VOL4″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL5 /dev/sdf1
Marking disk “VOL5″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm listdisks
VOL1
VOL2
VOL3
VOL4
VOL5
[root@node1 ~]#

Soft I/O error in ASM disk volume when using iostat commmand

Dear All,
We are having 2 node 11g rac/sun solaris 10/ASM storage, when we using iostat in node 2 getting soft I/O error keep on increasing.
s/w h/w trn tot device
*82 0 0 82 c4t600A0B80006766CD000003DF4B20A7FCd0*
s/w h/w trn tot device
0 0 0 0 md/d10
0 0 0 0 md/d11
0 0 0 0 md/d12
0 0 0 0 md/d20
0 0 0 0 md/d21
0 0 0 0 md/d22
0 0 0 0 md/d30
0 0 0 0 md/d31
0 0 0 0 md/d32
0 0 0 0 md/d40
0 0 0 0 md/d41
0 0 0 0 md/d42
0 0 0 0 md/d50
4 0 2 6 c0t0d0
0 0 0 0 c1t2d0
0 0 0 0 c1t0d0
0 0 0 0 c1t4d0
0 0 0 0 c1t1d0
2 0 0 2 c3t203200A0B86766CDd31
0 0 0 0 c4t600A0B80006766CD000003E14B20C891d0
40 0 0 40 c4t600A0B80006766CD000003DF4B20A7FCd0
0 0 0 0 c4t600A0B80006766CD000003DD4B20A57Fd0
0 0 0 0 c4t600A0B80006766CD000003C34B0D2D31d0
2 0 0 2 c4t600C0FF0000000000859635DB0097B00d0
2 0 0 2 c4t600C0FF000000000085963724A889B00d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F02d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F01d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F00d0
2 0 0 2 c2t202200A0B86766CDd31
0 0 0 0 c4t600A0B80006766CD000052274FD0B057d0
1 0 0 1 c4t600C0FF0000000000859635DB0097B02d0
2 0 0 2 c4t600C0FF000000000085963565767D300d0
2 0 0 2 c4t600C0FF00000000008596326C5F42901d0
1 0 0 1 c4t600C0FF00000000008596326C5F42900d0
1 0 0 1 c2t203300A0B86766CDd31
0 0 0 0 proddb2.zakathouse.org:vold(pid672)
please advice me how to troubshoot and fix this error
Thanks & Regards

Hi,
I suggest to have a look at following script which is provided by oracle to monitor IO.
ASMIOSTAT Script to collect iostats for ASM disks [ID 437996.1]
Further this i have questions
1) Are you logged in asm sysasm? Make sure that you have proper rights
2) Did you check the liveness of asm instance? Make sure its up and functional also check the asm alert.log for awareness.
Hope this helps

ASM disks in RAC need to be shared disks?

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

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

ASM Disk Sizes in a Disk Group

I have a Diskgroup that contains one ASMDisk that is 500gb. It needs to grow and my question is - Does the next disk added to the group need to be of the same size?
For example -
ASM_Disk1 = 500gb and is in ASM_Diskgrp1
ASM_Disk2 - 250gb >> can it be added to ASM_Diskgrp1
There is concern about balancing, etc. done by ASM
Wondering what experiences anyone has had with this?
Thanks!

Hi,
It's not mandatory, You can use disks with diferent sizes, but is extremally recomended that You put disks with the same size in a disk group.
you'd better use disks with the same storage capacity and performance.
The main reason is that ASM balances the I/O from all disks in a disk group due to this, put disks with the same same storage capacity and performance helps to improve the I/O and storage efficiently within the ASM disk group.
Regards,
Cerreia

Questions on asm disk discover:

Similar Messages

Maybe you are looking for