Asm disk showing as former

I have looked for ASM section with no luck. The issue I hope someone can help me solve is that I have dropped my diskgroups including contents and I am having problems creating the disk group again. It is not showing in the list of available disks. When I check all available disk it is showing as former. How can I re-use this?
Thanks

Hi,mention as Aman these disk groups still members of other diskgroups.However you can add these disks to desired diskgroup using following:
alter diskgroup <disk group> add disk <disk path> force; or
create diskgroup <disk group> normal redundancy
failgroup f1 disk <disk path> force
failgroup f2 disk <disk path> force;http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_5008.htm

Similar Messages

Asm disk showing as former after dropping disk groups

I used the excellent note by Vincent Chaun on installing RAC 10g on vmware and I got the RAC working. Exploring RAC, I dropped the disk groups and when I went to create it through dbca, it is only showing as former and not provisioned. Can anyone help on how to get this working? change.
Thanks

If the disk has been a member of the disk group and has been cleanly dropped, the header status will be FORMER. You can create the disk group on a disk which has a status of either of the followings:
CANDIDATE
FORMER
PROVISIONED
When this is the first time a disk has been created, the header status will be CANDIDATE. If the disk has been a member of the disk group and has been cleanly dropped, the header status will be FORMER. The PROVISIONED header status is similar to CANDIDATE except that PROVISIONED implies that an additional platform-specific action has been taken by an administrator to make the disk available for ASM. However, you can blow up the disk label by using 'dd' if you want to getrid of the FORMER header status but as said above you can create a diskgroup on disk that has header status FORMER.
Edited by: Gagandeep Arora on Jun 2, 2010 8:26 AM

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

Asm disk showing wrong usage

ASMCMD> lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 4096 1048576 819197 347946 0 347946 0 N FRA/
ASMCMD> cd FRA
ASMCMD> du PRD01/
Used_MB Mirror_used_MB
19973 19973
ASMCMD>
why is usable free MB is showing 347GB when i only used 20GB?
v11.2.0.2
Edited by: 800113 on 15-Feb-2012 14:54

800113 wrote:
ASMCMD> lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 4096 1048576 819197 347946 0 347946 0 N FRA/
ASMCMD> cd FRA
ASMCMD> du PRD01/
Used_MB Mirror_used_MB
19973 19973
ASMCMD>
why is usable free MB is showing 347GB when i only used 20GB? Its mirrored

ASM Disk Group Showing Full at 50%

Hi to all,
I have two sets of ASM disk groups, one I use for the main datafiles and the other I use for recovery.
The datafile ASM group is at 65% capacity. The Other "Recovery" Disk group became full at 50%, exactly half the size?!
Why does the group perform like this. It should be full when the disks are full? And why does the other group perform normally?
Has anyone else seen this problem before with ASM groups.
If anyone needs any more details please just ask me a question about it.
Thanks,
Jamie.

NAME PATH TOTAL_MB FREE_MB % Used DISK_NUMBER REDUNDA
STATE
DATA /dev/mapper/ASM1_V1p 35644 14389
60 9 NORMAL CONNECTED
1
DATA /dev/mapper/ASM14_V1 35644 14381
60 4 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM8_V1p 35644 14416
60 16 NORMAL CONNECTED
1
DATA /dev/mapper/ASM18_V1 35644 14389
60 8 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM16_V1 35644 14363
60 6 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM10_V1 35644 14335
60 0 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM4_V1p 35644 14415
60 12 NORMAL CONNECTED
1
DATA /dev/mapper/ASM15_V1 35644 14403
60 5 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM5_V1p 35644 14369
60 13 NORMAL CONNECTED
1
DATA /dev/mapper/ASM13_V1 35644 14331
60 3 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM2_V1p 35644 14393
60 10 NORMAL CONNECTED
1
DATA /dev/mapper/ASM11_V1 35644 14443
59 1 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM9_V1p 35644 14453
59 17 NORMAL CONNECTED
1
DATA /dev/mapper/ASM17_V1 35644 14401
60 7 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM7_V1p 35644 14443
59 15 NORMAL CONNECTED
1
DATA /dev/mapper/ASM3_V1p 35644 14342
60 11 NORMAL CONNECTED
1
DATA /dev/mapper/ASM6_V1p 35644 14428
60 14 NORMAL CONNECTED
1
DATA /dev/mapper/ASM12_V1 35644 14370
60 2 NORMAL CONNECTED
p1
RECOVERY /dev/mapper/ASM19_V1 139996 139842
0 0 NORMAL MOUNTED
p1
RECOVERY /dev/mapper/ASM22_V1 139996 139842
0 2 NORMAL MOUNTED
p1

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.

Difference between ASM Disk Group, ADVM Volume and ACFS File system

Q1. What is the difference between an ASM Disk Group and an ADVM Volume ?
To my mind, an ASM Disk Group is effectively a logical volume for Database files ( including FRA files ).
11gR2 seems to have introduced the concepts of ADVM volumes and ACFS File Systems.
An 11gR2 ASM Disk Group can contain :
ASM Disks
ADVM volumes
ACFS file systems
Q2. ADVM volumes appear to be dynamic volumes.
However is this therefore not effectively layering a logical volume ( the ADVM volume ) beneath an ASM Disk Group ( conceptually a logical volume as well ) ?
Worse still if you have left ASM Disk Group Redundancy to the hardware RAID / SAN level ( as Oracle recommend ), you could effectively have 3 layers of logical disk ? ( ASM on top of ADVM on top of RAID/SAN ) ?
Q3. if it is 2 layers of logical disk ( i.e. ASM on top of ADVM ), what makes this better than 2 layers using a 3rd party volume manager ( eg ASM on top of 3rd party LVM ) - something Oracle encourages against ?
Q4. ACFS File systems, seem to be clustered file systems for non database files including ORACLE_HOMEs, application exe's etc ( but NOT GRID_HOME, OS root, OCR's or Voting disks )
Can you create / modify ACFS file systems using ASM.
The oracle toplogy diagram for ASM in the 11gR2 ASM Admin guide, shows ACFS as part of ASM. I am not sure from this if ACFS is part of ASM or ASM sits on top of ACFS ?
Q5. Connected to Q4. there seems to be a number of different ways, ACFS file systems can be created ? Which of the below are valid methods ?
through ASM ?
through native OS file system creation ?
through OEM ?
through acfsutil ?
my head is exploding
Any help and clarification greatly appreciated
Jim

Q1 - ADVM volume is a type of special file created in the ASM DG. Once created, it creates a block device on the OS itself that can be used just like any other block device. http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000
Q2 - the asm disk group is a disk group, not really a logical volume. It combines attributes of both when used for database purposes, as the database and certain other applications know how to talk "ASM" protocol. However, you won't find any general purpose applications that can do so. In addition, some customers prefer to deal directly with file systems and volume devices, which ADVM is made to do. In your way of thinking, you could have 3 layers of logical disk, but each of them provides different attributes and characteristics. This is not a bad thing though, as each has a slightly different focus - os file system\device, database specific, and storage centric.
Q3 - ADVM is specifically developed to extend the characteristics of ASM for use by general OS applications. It understands the database performance characteristics and is tuned to work well in that situation. Because it is developed in house, it takes advantage of the ASM design model. Additionally, rather than having to contact multiple vendors for support, your support is limited to calling Oracle, a one-stop shop.
Q4 - You can create and modify ACFS file systems using command line tools and ASMCA. Creating and modifying logical volumes happens through SQL(ASM), asmcmd, and ASMCA. EM can also be used for both items. ACFS sits on top of ADVM, which is a file in an ASM disk group. ACFS is aware of the characteristics of ASM\ADVM volumes, and tunes it's IO to make best use of those characteristics.
Q5 - several ways:
1) Connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out. This creates an ADVM volume. Then, format the volume using 'mkfs' (*nix) or acfsformat (windows).
2) Use ASMCA - A gui to create a volume and format a file system. Probably the easiest if your head is exploding.
3) Use 'asmcmd' to create a volume, and 'mkfs' to format the ACFS file system.
Here is information on ASMCA, with examples:
http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348
Information on command line tools, with examples:
Basic Steps to Manage Oracle ACFS Systems

Strange issue in Oracle ASM on Two node RAC where in one ASM node shows all diskgroup while other node shows missing node.

We have Oracle datbase 11gR1 in RAC node with Oracle ASM.Recently our database server got crashed and we are trying to restore back services.
Using Snapshot technologyBusiness copy we had synced all our disk on storage level. Post this when we are trying to start ASM instance on node 1 it is coming and showing all diskgroups but on other node it is throwing errot with missing e diskgroup.
ORA-15032: not all alterations performed
ORA-15040: diskgroup is incomplete
ORA-15042: ASM disk "5" is missing
Expert please share your views.
Thanks,
Tushar

The I/O fabric layer on the other node failed to mount all storage LUNs - resulting in ASM being unable to mount a diskgroup as there are missing disks in that group.
Rebooting is exactly what could be needed to reset the h/w and infrastructure used by that node, in order for it to see all the storage disks again. As node 1 sees all storage disks (and is working), the disk itself on the storage system is intact and usable.
What is the o/s? What is the fabric layer? What is used on o/s for dealing with the I/O fabric layer?

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

Create ASM disks on Solarix X64 fails with ORA-15031

I am trying to create a ASM disk group on SOLARIS x64 using a NETAPP LUN. Below are the disks which are configured
SQL> show parameter asm;
NAME TYPE VALUE
asm_diskgroups string DATA
asm_diskstring string /dev/rdsk/c2t9*
asm_power_limit integer 1
asm_preferred_read_failure_groups string
bash-3.00# ls -ltr /dev/rdsk/c2t9d0s7
lrwxrwxrwx 1 root root 80 May 22 16:27 /dev/rdsk/c2t9d0s7 -> ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
bash-3.00# ls -ltr ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
crw-r----- 1 oracle dba 32, 583 May 22 16:56 ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
I get these errors when I try to create a disk group
SQL> create diskgroup DATA external redundancy disk '/dev/rdsk/c2t9d0s7';
create diskgroup DATA external redundancy disk '/dev/rdsk/c2t9d0s7'
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/rdsk/c2t9d0s7' matches no disks
ORA-15025: could not open disk '/dev/rdsk/c2t9d0s7'
ORA-15056: additional error message
Solaris-AMD64 Error: 13: Permission denied
Additional information: 42
Additional information: 198045856
Additional information: 198045848
Please help.

My guess is that you did not run fdisk and partition off the first 1M and ASM overwrote the VTOC rendering the device useless.
fdisk
create new partition
primary partition 1
start 2 end <last cylinder>
Then point your disk string to these partitions (<diskname>p1?)
Once this is done, I ALWAYS test to make sure the oracle AND grid user can read and write to this device from ALL nodes. I use the dd command to do this.
DO NOT DO THIS ON AN ALREADY CONFIGURED AND FUNCTIONING ASM DEVICE. Doing so will erase the device.
make a file in $HOME that contains one line:
cat <<EOF >> $HOME/x.x
this is a test
EOF
node1
dd if=$HOME/x.x of=<disk???p1> bs=20 count=1
node2
dd if=<disk???p1> of=$HOME/y.y bs=20 count=1 ##y.y should be the contents of node1:x.x
node1
dd if=/dev/zero of=<disk???p1> bs=8192 count=1000 ## erase the device for ASM usage.
Fix any read/write issues before proceeding.

ASM Disk Group RAID Levels

This is the scenario that I am currently working on. Just need some input on whether it is feasible or not.
We have a 2 node RAC running Oracle 10.2.0.3 on AIX 5L. Database size is ~2TB. The database mostly performs OLTP but also stores some historical data.
There are two main applications using the database - one performs high reads with some small updates & inserts, while the other is very write intensive but does some reads as well.
Currently there are three disk groups one for the tablespaces (dg_data), another for system/sysaux/undo tablespaces (dg_system) and another for archived logs & redo log copies (dg_flash) - all using external redundancy. ASM best practises recommend no more than 2 disk groups. It also recommends disk groups with disks of similar characteristics including raid levels. However, the dg_data disk group has both RAID 5 and RAID 1+0 disks which house tablespaces for both applications. Seeing that the applications have different requirements (heavy reads vs heavy writes) does it make sense to create a separate disk group with 2 different RAID levels or would using RAID 5 in dg_data satisfy both requirements?

I am attempting to generate some statistics on the ASM Disks I/O activity before implementing the disk group separation in order have some metrics for comparison purposes. Enterprise Manager Grid Control displays the performance of disk groups and individual disks by showing the Disk Group I/O Cumulative Statistics. When comparing the results with the asmiostat output I am unable to correlate the results. I know that the asmiostat queries the v$asm_disk_stat view. Where does EM GC pull it's information from?
For example, I run the following query on the ASM instance:
SQL> select group_number,disk_number,total_mb,free_mb,name,path,reads,writes,read_time,write_time,bytes_read,bytes_written
2 from v$asm_disk_stat
3 where group_number=
4 (select group_number from v$asm_diskgroup
5* where name = 'DG_FLASH')
GROUP_NUMBER DISK_NUMBER TOTAL_MB FREE_MB NAME PATH READS WRITES READ_TIME WRITE_TIME BYTES_READ BYTES_WRITTEN
1 0 8671 8432 DG_FLASH_0000 /dev/asm2 14379476 10338479 149205.75 19633.64 290,136,450,560.00 7.2165E+10
1 1 8671 8431 DG_FLASH_0001 /dev/asm3 11470508 10278698 184597.5 19313.54 249,769,027,584.00 9.2911E+10
1 2 8671 8432 DG_FLASH_0002 /dev/asm4 17274529 8743188 178547.56 38342.52 339,439,240,192.00 6.7165E+10
The output from the same period on Grid Control is below
MEMBER DISKS AVG RESPTIME AVG THROUGHPUT TOT I/O TOT RDS TOT WRTS RDERRS WRTERRS
DG_FLASH_0000 5.58 2.58 33179503 21949607 11,229,896 0 0
DG_FLASH_0001 8.26 1.83 25752100 13131695 12,620,405 0 0
DG_FLASH_0002 8.11 1.86 28269693 18798823 9,470,870 0 0
The statistics in the query are lower than those in the EM GC report. I also tried querying the fixed views (x$) but the results were even more confusing.
What is the best method for comparing and gathering statistics on ASM activity?

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 added without scan on second node

Hi All ,
Oracle Version:11.2.0.3
I need one help for one issue with ASM disk addition.
It is a two node RAC and one disk group was filled.
One disk was available as UNUSED001 and so we renamed it ran scan disk and added the disk to the diskgroup on node1.
But , as we did not run the scan disk on second node , the name is still showing as UNUSED001 and assigned to diskgroup so showing as MEMBER.
Also, the renamed disk is also showing as MEMBER but not assigned with any diskgroup.
Usually, when this heppens we have to reboot the node to fix the issue , but would like to get idea if this can be fixed without bouncing nodes.

Hi ,
+ Probably that disk addition failed with ORA-15075 as same named device is not visible after renaming of disk.
As this validation takes place after writing disk header ,it is showing as MEMBER.
+ Get downtime of cluster on 2nd node and run scandisks on 2nd node.
+ Now renamed disk should be showing up on node 2.
+ if showing up ,then validate .
-- All expected diskgroups were mounted on both nodes or not
sql> select inst_id,name,state from gv$asm_diskgroup;
-- If mounted validate that renamed disk group_number and mount_status
sql> col path for a30
sql> select inst_id,group_number,path,mount_status from gv$asm_disk;
+ If group_number is 0 and mount_status is CLOSED ,then it is not part of any mounted diskgroup.
Add that disk again with force option in same diskgroup.
sql> alter diskgroup <diskgroup_name> add disk 'ORCL:<LABEL_NAME>' force;
And allow rebalance to complete.
Regards,
Aritra

ASM disk busy 99% only on one cluster node

Hello,
We have a three node Oracle RAC cluster. Our dba(s) called us and said they are getting OEM critical alers for an asm disk on one node only. I checked and the SAN attached drive does not show the same high utilization on either of the other two nodes. I checked the hardware and it seems fine. If the issue was with the SAN attached disk, we would be seeing the same errors on all three nodes since they share the same disks. The system crashed last week(alert dump in the +asm directories), and at the disk has been busy ever since. I asked if the dba reviewed the ADDM reports and he said he had and that there were no suspicious looking entries that would lead us to the root cause based on those reports. CPU utilization is fine. I am not sure where to look at this point and any help pointing me in the right direction would be appreciated. They do use RMAN, could there be a backup running using those disks only on one node? Has anyone ever seen this before?
Thank you,
Benita Ulisano
Unix/SAN Team
Chicago Public Schools
[email protected]

Hi Harish,
Thank you for responding. To answer your question, yes, the disks are all of the same spec and are shared among the three cluster node. The asm disk sdw1 is the one with the issue.
Problem Node: coefsdb02
three nodes in RAC cluster
coefsdb01, coefsdb02, coefsdb03
iostat results for all three nodes - same disk
coefsdb01
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util
sdw1 0.00 1.71 0.12 0.58 1.27 18.78 28.63 0.01 13.38 1.75 0.12
coefsdb02
sdw1 0.11 0.02 4.00 0.62 305.84 21.72 70.93 2.96 12.58 211.95 97.88
coefdb03
sdw1 0.21 0.01 4.70 0.33 224.05 13.52 47.22 0.05 10.11 6.15 3.09
The dba(s) run RMAN backups, but only on coefsdb01.
Benita

Problem creating asm disk groups after installation.

I just completed the grid install successfully on Oracle Linux:
Candidate ASM disks not showing up in 11.2 installer (Oracle Linux)
Thanks for the help.
I am running into the same type of issue where I can't see the asm disks like I ran ran into during the install.
When I run asmca to create the addditional disk groups I don't see the two asmlib volumes.
I tried changing the disk discovery path from the default and I still can't see the disks.
$ /usr/sbin/oracleasm listdisks
CRSVOL1
DATAVOL1
FRAVOL1
Do the block devices need to be owned by grid?
$ ls -l /dev/sdc
brw-r----- 1 root disk 8, 32 Aug 2 15:21 /dev/sdc
$ ls -l /dev/sdd
brw-r----- 1 root disk 8, 48 Aug 2 15:21 /dev/sdd
$ ls -l /dev/sde
brw-r----- 1 root disk 8, 64 Aug 2 15:21 /dev/sde
How can the installer work fine and see the disks and then asmca can't see the disks?
It must be a permissions issue. How can I see what the error is that is preventing the disks from showing up?

$ cd /dev/oracleasm
node 2:
$ cd /dev/oracleasm
$ ls -lL
total 0
-rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .check_iid
drwxr-xr-x 1 root root 0 Aug 15 11:08 disks/
-rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .get_iid
drwxrwx--- 1 grid asmadmin 0 Aug 15 11:08 iid/
-rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .query_disk
-rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .query_version
$ ls -lL disks/*
brw-rw---- 1 grid asmadmin 8, 33 Aug 15 11:08 disks/CRSVOL1
brw-rw---- 1 grid asmadmin 8, 49 Aug 15 11:08 disks/DATAVOL1
brw-rw---- 1 grid asmadmin 8, 65 Aug 15 11:08 disks/FRAVOL1
node 1:
$ cd /dev/oracleasm
$ ls -lL
total 0
-rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .check_iid
drwxr-xr-x 1 root root 0 Aug 15 12:30 disks/
-rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .get_iid
drwxrwx--- 1 grid asmadmin 0 Aug 15 12:30 iid/
-rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .query_disk
-rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .query_version
$ ls -lL disks/*
brw-rw---- 1 grid asmadmin 8, 33 Aug 15 12:30 disks/CRSVOL1
brw-rw---- 1 grid asmadmin 8, 49 Aug 15 12:30 disks/DATAVOL1
brw-rw---- 1 grid asmadmin 8, 65 Aug 15 12:30 disks/FRAVOL1

Asm disk showing as former

Similar Messages

Maybe you are looking for