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

Similar Messages

Create ASM Disk Groups cannot see Disk Path to select during installation

Hello Guys,
I am setting up 2 node RAC on 11gR2 and Linux.
I have configured all the pre-installation steps that are required to run Grid Setup as per my understanding.
I have configure SAN partitions using multipath.
I can see my SAN volume when i query multipath -l
Then i configured the raw partitions by oracleasm. Configured and then created mount points:
/dev/oracleasm/disks/
CRSVOL1 DATAVOL1 FRAVOL1
Later on I created the disks using oracle asm command:
/usr/sbin/oracleasm createdisk CRSVOL1 /dev/mapper/racdbp1 and so on...
I have run /usr/sbin/oracleasm scandisks
Cleaning any stale ASM disks...
Scanning system for ASM disks...
And when i list disk with command /usr/sbin/oracleasm listdisks
it shows the disk like this on both nodes:
CRSVOL1
DATAVOL1
FRAVOL1
BUT during the installation screen when it comes to create ASM Disk Groups It shows nothing in the add disk frame, I cant select the volumes I can list, like i did above.
Any hint please?
Thanks, Imran

Thanks but my problem is very specific. I feel that i have performed all the necessary steps to get complete the step i discussed above. As per different commands all is set. But i am unable to see Disks and Disks Paths during the installation screen. This is another output to verify if the installe user have rights on the asm devices:
[grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
DATAVOL1 ETSCRS1 ETSVOT1 ETSVOT3 FRAVOL1
ETSASM1 ETSCRS2 ETSVOT2 EXTRADM
[grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
[grid@racnode1 disks]$ ls -ltr
total 0
brw-rw---- 1 grid asmadmin 8, 1 Oct 2 16:47 ETSASM1
brw-rw---- 1 grid asmadmin 8, 5 Oct 2 16:47 DATAVOL1
brw-rw---- 1 grid asmadmin 8, 6 Oct 2 16:47 FRAVOL1
brw-rw---- 1 grid asmadmin 8, 7 Oct 2 16:47 ETSVOT1
brw-rw---- 1 grid asmadmin 8, 8 Oct 2 16:47 ETSVOT2
brw-rw---- 1 grid asmadmin 8, 9 Oct 2 16:47 ETSVOT3
brw-rw---- 1 grid asmadmin 8, 10 Oct 2 16:47 ETSCRS1
brw-rw---- 1 grid asmadmin 8, 11 Oct 2 16:47 ETSCRS2
brw-rw---- 1 grid asmadmin 8, 13 Oct 2 16:47 EXTRADM
I will appreciate if you can help me to get through this step... Is there anything else needs to be verified?
Regards, Imran

Can not find disks when creating ASM disk group (11.0.2.3 on OEL 6)

Hi
I`m trying to install 11.0.2.3 Grid on OEL6.
Every thing is fine until it prompt to ask where I want to put OCR and VOTING DISK. I choose to put them in ASM. So it prompt another window to ask create ASM DISK GROUP.
In this window there was an area called "add disk". There suppose to be some disks listed in this area to chose. But in my case, nothing here. I can not chose disks to add to ASM DISK GROUP.
Below are descriptions of my installation.
Oracle Grid 11.0.2.3
OEL 6 as the platform.
I use two nodes mounting the same NFS. I created some zero-padded files on the NFS directory as the ASM DISKS. (This disks should be showing the the area above)
I install everything using only one account oracle. The group is oinstall and dba
Edited by: Kramer on Jun 5, 2013 8:52 PM

Well as i see your asm_diskstring could be the problem. ASMlib would have been there isnt it , I would want you to stick to default value and then try also I would suggest you to once post the output of the following and lets see whats happening
[root@ora ~]# /etc/init.d/oracleasm scandisks
[root@ora ~]# /etc/init.d/oracleasm listdisks
[root@ora ~]# ls -ltr /dev/oracleasm/disks/*

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 ~]#

Cleaning up ASM disk group after failed rman duplicate session?

I am using rman duplicate to create a clone of a production database. The rman duplicate failed in phase 1 (retoration of datafiles) and my datafile are being restored to an ASM diskgroup.
I read in the metalink note Manual Completion of a Failed RMAN Duplicate [ID 360962.1] the following...
Note : From 10g onwards, if duplicate failed during step 1, which is the restore of datafiles, it is probably best to restart the duplicate process. Any files that have already been restored will be skipped and the duplicate process can continue without manual intervention
So I followed the advice in the note and started the rman duplcate script over again from the beggining. I am hoping it will have the intelligence to skip any files that have already been restored but if it is not since this is 10.1.0.3 and I cannot use the asmcmd command to connect to the ASM instance to delete any files that have been created then how can I delete and of the files since the database instance never got created correctly and cannot open?
Any thought on how I can now cleanup the files in the ASM disk group? Also, has anyone started an rman duplicate again after it has previously failed and did it actually skip the files that are already there as stated in the metalink note?
Thanks.

Unfortunately the v$asm_file does not have the entire file name or path it just gives you the follwing...
SQL> desc v$asm_file
Name Null? Type
GROUP_NUMBER NUMBER
FILE_NUMBER NUMBER
COMPOUND_INDEX NUMBER
INCARNATION NUMBER
BLOCK_SIZE NUMBER
BLOCKS NUMBER
BYTES NUMBER
SPACE NUMBER
TYPE VARCHAR2(64)
REDUNDANCY VARCHAR2(6)
STRIPED VARCHAR2(6)
CREATION_DATE DATE
MODIFICATION_DATE
This really stinks I wish I didn't have to work with 10gr1 at all but the database I am trying to move to a ew server and new storage is running this version and we did not want to upgrade the existing database first before attempting the migration because it is reliant upon tape backups which I do not have alot of confidence in...

Cannot create ASM disk groups in DBCA - Oracle 11gR1, Windows 32bit

Good afternoon,
Using 11gR1 on Windows XP, I need help installing a database (single instance) using ASM, I am not able to select disks to be stamped for use by ASM. I have done the following steps:
1. Installed the Oracle 11gR1 software (no database created - just the software)
2. Connected nine (9) SCSI hard drives to the system
3. Created a primary partition on each hard drive, formatted the partition but did *not* assign a drive letter
4. Created a listener service (working properly - checked with lsnrctl status)
5. Started DBCA to create a single database instance using ASMIn DBCA I performed the following:
a. at the welcome screen, click Next
b. at "Step 1 of 16", click Next (accepting the default "Create a Database")
c. at "Step 2 of 16", click Next (accepting the default "General Purpose or Transaction Processing)
d. at "Step 3 of 16", "Global Database Name" set to "dbca", "SID" set to "dbca", click Next
e. at "Step 4 of 16", click Next (accepting the defaults)
f. at "Step 5 of 16", click "Use same administrative passwords for all accounts" and entered password, click Next
g. at "Step 6 of 16", click "Automatic Storage Management (ASM)", click Next
Everything seems just fine until I reach the following step
h. at "Step 7 of 16", click "Create New"
    - The Create Disk Group window pops up (there is nothing shown in the "Select Member Disk Area")
    - set the "Disk Group Name" to "DATAGROUP"
    - click on "Show All" (no devices shown after clicking)
    - click on "Stamp Disks..." this causes the "asmtool operation" window to pop up
      - click on "Add or change label", click on Next
      - the "Select Disks" step appears.   There are 11 hard drives listed but NONE of them
        can be selected - all I can do here is click on Cancel*The question:* Why aren't the drives selectable and what do I need to do to make them selectable ?
Thank you very much for your help,
John.

>
The question: Why aren't the drives selectable and what do I need to do to make them selectable ?
>
To answer my own question (now that I've figured it out), the reason is because the partition should not be formatted.
When Windows displays the "New Partition Wizard", it is important to:
1. not assign a drive letter
2. and select "Do not format this partition"
This will cause Windows to mount the volume thus making it accessible to Oracle.
Hopefully this will help someone not fall in this trap as I did,
John.

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

Getting errors while creating asm disk groups

while creating disk groups on 10gR2 database on linux redhat 5.3
im getting following errors :
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/raw/raw4' matches no disks
ORA-15025: could not open disk '/dev/raw/raw4'
ORA-27041: unable to open file
Linux Error: 19: No such device
Additional information: 42
Additional information: 213402552
Additional information: -1079643768
ORA-15031: disk specification '/dev/raw/raw3' matches no disks
ORA-15025: could not open disk '/dev/raw/raw3'
ORA-27041: unable to open file
Linux Error: 19: No such device
Additional information: 42
Additional information: 213402552
Additional information: -1079643768
ORA-15031: disk specification '/dev/raw/raw2' matches no disks
ORA-15025: could not open disk '/dev/raw/raw2'
ORA-27041: unable to open file
Linux Error: 19: No such device
Additional information: 42
Additional information: 213402552
Additional information: -1079643768
ORA-15031: disk specification '/dev/raw/raw1' matches no disks
ORA-15025: could not open disk '/dev/raw/raw1'
ORA-27041: unable to open file
Linux Error: 19: No such device

these are contents of my initORCL.ora :
ORCL.__db_cache_size=251658240
ORCL.__java_pool_size=4194304
ORCL.__large_pool_size=4194304
ORCL.__shared_pool_size=104857600
ORCL.__streams_pool_size=0
*.audit_file_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/adump'
*.background_dump_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/bdump'
*.compatible='10.2.0.1.0'
*.control_files='/opt/oracle/product/10.2.0/oradata/ORCL/control01.ctl','/opt/oracle/product/10.2.0/oradata/ORCL/control02.ctl','/opt/oracle/product/10.2.0/oradata/ORCL/control03.ctl'
*.core_dump_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='ORCL'
*.db_recovery_file_dest='/opt/oracle/product/10.2.0/db_1/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=ORCLXDB)'
*.job_queue_processes=10
*.local_listener='LISTENER_ORCL'
*.log_archive_dest='/opt/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/archives'
*.log_archive_format='PROD_%t_%s_%r.ARC'
*.log_archive_start=TRUE
*.open_cursors=300
*.pga_aggregate_target=121634816
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=365953024
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/udump'
these are contents of init+ASM.ora
# Automatic Storage Management
# asmallow_only_raw_disks=false
# asm_diskgroups='TESTDB_DATA1'
# Default asm_diskstring values for supported platforms:
# Solaris (32/64 bit) /dev/rdsk/*
# Windows NT/XP \\.\orcldisk*
# Linux (32/64 bit) /dev/raw/*
# HPUX /dev/rdsk/*
# HPUX(Tru 64) /dev/rdisk/*
# AIX /dev/rhdisk/*
# asm_diskstring=''
# Diagnostics and Statistics
background_dump_dest=/opt/oracle/product/10.2.0/db_1/admin/+ASM/bdump
core_dump_dest=/opt/oracle/product/10.2.0/db_1/admin/+ASM/cdump
user_dump_dest=/opt/oracle/product/10.2.0/db_1/admin/+ASM/udump
# Miscellaneous
instance_type=asm
##compatible=10.1.0.4.0
compatible=10.2.0.1.0
DB_UNIQUE_NAME=+ASM
# Pools
large_pool_size=12M
# Security and Auditing
remote_login_passwordfile=exclusive
disk groups are succcesfully configured but my database is still showing old file system.
please guide
Edited by: user13376823 on Oct 22, 2012 10:35 AM

Creating ASM disk group

Hi,
I have a 2-node RAC. I want to add a new diskgroup, to ASM.
At the first node, I run the CREATE DISKGROUP command. I though the disk group would appear at second node's ASM and I would only have to mount. But on the second node EM, the disk group does not appear in V$ASM_DISK and the ALTER DISKGROUP MOUNT command returns ORA-15063.
Do I have to create the disk at the second node too?
Edited by: user492400 on Mar 30, 2010 12:40 PM

how you created disks on node #1?
did you use oracleasm createdisk command?
run sudo /etc/init.d/oracleasm scandisk on node#1 then same command on node#2
then run /etc/init.d/oracleasm listdisks on both nodes and compare result.
if you see all disks correctly on both nodes, then connect to ASM on node#2 and run
ALTER DISKGROUP ALL MOUNT;
new diskgroup should be mounted.

Problem in ASM Disk Groups / Instance startup

Hi,
I got ORA-15041 when trying to add a datafile to a tablespace in 11gR2 RAC in RHEL 5.4.
In order to solve that, I would do a ALTER DISKGROUP .. RESIZE DISK command.
But to do that, I think I should startup an ASM instance.
I created a file /tmp/init+ASM.ora (with INSTANCE_TYPE=ASM), connected to an idle instance, created an spfile from pfile = '/tmp/init+ASM.ora';
When I try to startup nomount, I get ORA-01031.
Any idea?
Thanks

[oracle@yyyy bin]$ env | sort
_=/bin/env
CLASSPATH=/u01/app/oracle/product/11.2.0/db_1/JRE:/u01/app/oracle/product/11.2.0/db_1/jlib:/u01/app/oracle/product/11.2.0/db_1/rdbms/jlib
CVS_RSH=ssh
G_BROKEN_FILENAMES=1
HISTSIZE=1000
HOME=/home/oracle
HOSTNAME=yyyy.xxxx.local
INPUTRC=/etc/inputrc
LANG=en_US.UTF-8
LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/db_1/lib:/lib:/usr/lib
LESSOPEN=|/usr/bin/lesspipe.sh %s
LOGNAME=oracle
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:
MAIL=/var/spool/mail/oracle
OLDPWD=/u01/app/oracle/product/11.2.0/xxxx
ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/11.2.0/xxxx/
ORACLE_HOSTNAME=yyyy.xxxx.local
ORACLE_SID=+ASM
ORACLE_TERM=xterm
PATH=/u01/app/oracle/product/11.2.0/db_1/bin:/usr/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oracle/bin
PWD=/u01/app/oracle/product/11.2.0/xxxx/bin
SHELL=/bin/bash
SHLVL=1
SSH_CLIENT=192.168.10.113 1137 22
SSH_CONNECTION=192.168.10.113 1137 192.168.10.24 22
SSH_TTY=/dev/pts/1
TERM=xterm
TMPDIR=/tmp
TMP=/tmp
USER=oracle

Error while creating asm disk group:::urgent

i am getting this error though i have given total path in DISK parameter.
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK 'disk1'
5 FAILGROUP ctlr2
6 DISK 'disk2';
CREATE DISKGROUP dgroup1
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification 'disk2' matches no disks
ORA-15031: disk specification 'disk1' matches no disks

hi all,
thnx for ur attention i am able to solve the issue by doing the following steps...
[oracle@sierra200 product]$ su - root
Password:
[root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk1
[root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk2
ioctl: LOOP_SET_FD: Device or resource busy
[root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk1
ioctl: LOOP_SET_FD: Device or resource busy
[root@sierra200 root]# losetup /dev/loop2 /u04/app/oracle/product/asmdisks/disk2
[root@sierra200 root]# vi /etc/sysconfig/rawdevices
# raw device bindings
# format: <rawdev> <major> <minor>
# <rawdev> <blockdev>
# example: /dev/raw/raw1 /dev/sda1
# /dev/raw/raw2 8 5
/dev/raw/raw1 /dev/loop1
/dev/raw/raw2 /dev/loop2
[root@sierra200 root]# /etc/init.d/rawdevices start
Assigning devices:
/dev/raw/raw1 --> /dev/loop1
/dev/raw/raw1: bound to major 7, minor 1
/dev/raw/raw2 --> /dev/loop2
/dev/raw/raw2: bound to major 7, minor 2
done
[root@sierra200 root]# chown oracle:dba /dev/raw/raw1
[root@sierra200 root]# chown oracle:dba /dev/raw/raw2
[root@sierra200 root]# chmod 660 /dev/raw/raw1
[root@sierra200 root]# chmod 660 /dev/raw/raw2
[root@sierra200 root]# exit
logout
shut the instance and make the disk string as '/dev/raw/raw*'
and then create spfile from pfile. and then nomount the instance.
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK '/dev/raw/raw1'
5 FAILGROUP ctlr2
6 DISK '/dev/raw/raw2';
Diskgroup created.
SQL> select name, state,total_mb,free_mb,path from v$ASM_DISK;
NAME STATE TOTAL_MB FREE_MB
PATH
DGROUP1_0001 NORMAL 100 50
/dev/raw/raw2
DGROUP1_0000 NORMAL 100 50
/dev/raw/raw1
Regards,
Sravan

ASM disk group and multiple databases

Hi,
I want to create a second database on my RAC cluster. Can the ASM diskgroups I have defined for use with the first database , service the second database or do I have to create another set of ASM diskgroups for the second dataabase?
Thanks,
Anne

ASM does not have any data files. ASM will store data files required for the RDBMS instance only.
After you have installed the Oracle binaries, (best practice is to have two Oracle homes one for ASM and another for RDBMS), you can create the ASM instances using DBCA and during this process or later can create ASM diskgroups.
( e,g disk1G, disk2G,disk3G,disk4G) using the above four you can create ASM DISK GROUPS..

Recover OCR and VOTE disk after complete corruption of ASM disk groups.

Hi Gurus,
I am simulating a recovery situation to perform recover of OCR and Vote files after complete corruption of ASM related disks and diskgroups. I have setup my environment as follows:\
Environment: RAC
OS: OEL 5.5 32-bit
GI Version: 11.2.0.2.0
ASM Disk groups: +OCR, +DATA
OCR, Vote Files location: +OCR
ASM Redundancy: External
ASM Disks: /dev/asm-disk1, /dev/asm-disk2
/dev/asm-disk1 - mapped on +OCR
/dev/asm-disk2 - mapped on +DATA
With the above configuration in place I have manually corrupted +OCR, +DATA diskgroups with dd command. I used this command to completely corrupt +OCR disk group.
dd if=/dev/zero of=/dev/asm-disk1. I have manual backups as well as automatic backups of OCR and Vote disk. I am not using ASMLib.
I followed this link:
http://docs.oracle.com/cd/E11882_01/rac.112/e17264/adminoc.htm#TDPRC237
When I tried to recover OCR file, I could not do so as there is no such diskgroup which ASM can restore the OCR, Voting disk to. I could not Re-create OCR and DATA diskgroups as I cannot connect to ASM instance. If you have a solution or workaround for my situation please describe it. That will be greatly appreciated.
Thanks and Regards,
Suresh.

Please go through the following document which have the detailed steps to restore the OCR
How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems [ID 1062983.1]

Reinstalling Oracle 11gR2 RAC Grid Problem - ASM Disks Group

Folks,
Hello.
I am installing Oracle 11gR2 RAC using 2 Virtual Machines (rac1 and rac2 whose OS are Oracle Linux 5.6) in VMPlayer.
I have been installing Grid Infrastructure using runInstaller in the first VM rac1 from step 1 to step 9 of 10.
On the step 9 of 10 in the Wizard, accidentally, I touch the Mouse, and the Wizard is gone.
The directory for installing Grid in the 2 VMs is the same: /u01
In order to make sure everything is correct, I delete entire directory /u01 in the 2 VMs and install Grid in rac1 again.
I have understood it's not the right way to delete /u01. The right way is to follow the tutorial
http://docs.oracle.com/cd/E11882_01/install.112/e22489/rem_orcl.htm#CBHEFHAC
But I have deleted /u01 and need to fix one by one. I install Grid again and get the error message on step 5 of 9 as follows:
[INS - 30516] Please specify unique disk groups.
[INS-3050] Empty ASM disk group.
Cause - Installer has detected the disk group name provided already exists on the system.
Action - Specify different disk group.
In Wizard, the previous Disk Group name is "DATA" and its Candidate disks (5 ASMDISKs) are gone. I try to use a different name "DATA2", but no ASMDISKs come up under "Candidate disks". For "ALL Disks", all ASMDISKs cannot be selected.
I want to use the same ASM disk group "DATA" and don't want to create a new disk group.
My question is:
How to have the previous ASM disks and its group "DATA" come up under "Candidate Disks" so that can use it again ?
Thanks.

Hi, in case this helps anyone else. I got this INS-30516 error too was stumped for little while. I have 2 x 2-node RAC which are hitting same SAN. The first-built RAC has a DATA diskgroup. When went to build second RAC on new ASM disk new DIskgroup (but same diskgroup name DATA) got INS-30516 about diskgroup name already in use etc. Finally figured out all that was required was to restrict diskstring using button in installer to only retrieve the LUNS for this RAC (this was quick and dirty - all LUNS for both RAC being presented to both RAC). Once diskstring only searched for the LUNS required for this RAC only, e.g.
ORCL:DATA_P* (for DATA_PD and FRA_PD)
the error went away.
I also have DATA_DR and FRA_DR presenting to both RAC. Apparently it scans the header and if it finds a diskgroup name that is already in use based on the diskstring scan it will not allow reuse of the diskgroup name since it has no way of knowing that the other ASM disks are for a different RAC.
HTH

How reInstall Gride Infrastructure and Use old ASM disk groups

<pre>Hello to all
I installed Grig Infrastructure 11gR2 on a standalone server (OS is Linux)
and I configured ASM and my database created on ASM
Conceive that my OS disk corrupted and OS doesn't start and the Gride Home is on that disk,
and I have to install OS again
My ASM disks are safe , Now how can I install Grig Infrastructure again somehow that it can use previous ASM disks
and disk groups and I don't oblige to create my database again ?
In the step 2 of installing Gride Infrastructure it has four options
<pre>
1.Install and configure Oracle Grid Infrastructure for a Cluster
2.Configure Oracle Grid Infrastructure for a Standalone Server
3.Upgrade Oracle Gride Infrastructure or Oracle Automatice Storage Management
4.Install Oracle Gride Infrastructure Software Only
</pre>
If I select the option 2 it wants to create a disk group again
I guess that I need to select option 4 and then do some configuration but I don't know what I must configure
Do you know answer of my question , if yes please explain it's stages
Thank you so much
</pre>

Hi,
no you are not obliged to recreate your database again. However there is a small flaw in the installation procedure, which does not make it 100% easy...
When you installed the Oracle Restart (Standalone GI), your ASM diskgroup will contain the SPFILE of the ASM instance. And this is exactly the small flaw you will be encountering. So you have 2 options for "recovery":
1.) Do a software only install (4), and run roothas.pl. This however will not create any ASM entries. You would have to add it manually (using srvctl) and you can specify the ASM Spfile with the srvctl command. Problem here is however to have to know where your ASM spfile has been. If you have a backup of your OLR and a backup of the GPNP profile, this might be easier to find out.
2.) Do a new installation (2) and configure a new diskgroup (with a "spare" disk or small lun and a new name), that Oracle restart creates ASM instance and the new ASMSpfile for you.
Then you can simply mount the diskgroup containing your database additionally. You then shoudl however move your new ASMSpfile to the new diskgroup (or simply exchange it with the existing one). In this case it is easier to find out where it was - however you will need a spare (though small) LUN for the new spfile (temporarily, until you exchange it).
In either case after you have your ASM instance back (and access to your old diskgroup), you have to reregister your database and services - if you do not have an OLR backup.
Again => It is doable and you can simply mount the ASM diskgroup containing your database. However I suggest you try this one time to know what really needs to be done in this case.
Regards
Sebastian

Problem creating asm disk groups after installation.

Similar Messages

Maybe you are looking for