Create ASM Failure Group via dbca

I am not sure how to configure a Failure Group in ASM.
I am not using asmlib.
So I start dbca - choose configure ASM
Create Diskgroup --> Data
select my 2 raw devices ( which are on 2 storages)
I select normal redundancy;
Disk Path ASM Name Failure Group
/dev/raw/raw4 Data1 FG1_Data
/dev/raw/raw5 Data2 FG2_Data
Is this enough ? Or is there anything else needed for a functional failure group ?
Does that mean, when one storage (with disk Data2) is switched off - that my instance will survive and is still able to write data on the diskgroup ?

Hi,
What is your oracle version?

Similar Messages

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.

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/*

ASM Failure Groups

Hello everyone,
on 10204,
currently my database uses ASM & is of externel redundancy.
I've to mirror the entire set of disks to another set of disks.
I'm planning to use ASM failure groups for that.
can anybody provide useful links for that feature. Can't get much idea from oracle doc
thanks

Hi;
How To Add Back An ASM Disk or Failgroup (Normal or High Redundancy) After A Transient Failure Occurred (On Release 10.2. or 10.1)? [ID 946213.1]
ASM Technical Best Practices [ID 265633.1]
Also see:
Master Note for Automatic Storage Management (ASM) [ID 1187723.1]
ASM Management
http://www.oracle-base.com/articles/10g/AutomaticStorageManagement10g.php
Regard
Helios

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

ASM Failure Groups and Disk Controllers

Hey guys,
I understand that it's considered a good idea to set different Failure Groups for disks which could fail at the same time because they share hardware, For example, disks that share the same disk controller.
Now, my question might be silly but I don't understand why we would configure multiple disks with the same disk controller.
Thank you,
Jerry.

Jerry wrote:
Hey guys,
I understand that it's considered a good idea to set different Failure Groups for disks which could fail at the same time because they share hardware, For example, disks that share the same disk controller.
Now, my question might be silly but I don't understand why we would configure multiple disks with the same disk controller.
Hi Jerry,
Your question is not silly.
Usually you have one or more disk controllers in a system
Each controller can handle up to x disks ( in the past this was 15, don't know if this still is )
If you wanted to be redundant, like with RAID1 ( mirrorring ) configurations a system was usually configured to have an even amount of disks
spread evenly over two controllers.
This then covered disk-failure and controller failure, as each logical disk in the mirror-set is accessible over two controllers and consists of -at least - two disks.
In ASM you would configure the main diskgroup on the first set of disks on the first controller.
The failure group would then be configured on the second set of disks on the second controller.
In the SAN world, with ASM using Host Based Mirroring, the Failure group can also be a diskset on a totally different storage-server
Edit: Totally forgot: More disks on one controller mean more parallel access to your data, as you can read all seperate disk seperately.
In the current days with the enormous disks it is quite easy to configure just one disk in your system, but that will bring you quite easy huge performance problems
HTH
FJFranken
Edited by: fjfranken on 20-jul-2011 6:53

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

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

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.

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

How to define ASM failure groups!

Hi all,
I have 4 disk on both disk controller
SATA controller
ASMDISKO1
ASMDISKP1
SCSI controller
ASMDISKR1
ASMDISKS1
I created diskgroup test as below:
CREATE DISKGROUP TEST EXTERNAL REDUNDANCY
FAILGROUP controller1 DISK 'ORCL:ASMDISKO1', 'ORCL:ASMDISKP1',
FAILGROUP controller2 DISK 'ORCL:ASMDISKR1', 'ORCL:ASMDISKS1';
but i got this error:
ERROR at line 2:
ORA-15106: missing or invalid operating system disk locator string
Please help!
Thank you!

What does controller1 means and where can i find it? do i need to put in the create diskgroup like the example? its a failgroup name since we're creating DG with normal redundancy, after creating it you can find detail on this from v$asm_disk
see below example.
creating diskgroup with NORMAL REDUNDANCY with 2 disk (68gb each)
CREATE DISKGROUP TEST NORMAL REDUNDANCY
FAILGROUP controller1 DISK
    '/dev/rhdiskpower8'
   FAILGROUP controller2 DISK
'/dev/rhdiskpower9' ;
ASMCMD> lsdg
State    Type    Rebal Unbal Sector Block       AU Total_MB Free_MB Req_mir_free_MB *Usable_file_MB* Offline_disks Name
MOUNTED NORMAL N      N         512   4096 1048576    139424   139322                0           69661              0 TEST/
ASMCMD>
SQL> select GROUP_NUMBER ,NAME from v$asm_diskgroup;
GROUP_NUMBER NAME
           5 TEST
SQL> select GROUP_NUMBER,FAILGROUP,label ,path from v$asm_disk;
GROUP_NUMBER FAILGROUP                      LABEL                           PATH
           5 CONTROLLER1                                                    /dev/rhdiskpower8
           5 CONTROLLER2                                                    /dev/rhdiskpower9Please close the thread if you feel you have the answer and keep the Oracle forum clean.
https://forums.oracle.com/forums/ann.jspa?annID=885
Thanks
Kuljeet Pal Singh

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

Creating ASM

Please, can someone put me through on how to create ASM disk groups?
I've tried it severally with the DBCA but I don't quite get it.
Actually, I want to create a Database that uses ASM. Incase, you want
to give me a link to read about ASM ... I've tried that.
All I need is the steps you used in creating yours, possibly.
Regards,
Cherish

ASM is a way of using plain raw disk partitions without having a file system on the partition.
Since you do not specify Operating System, I will lump you in with the traditional Windows user who generally does not specify operating system.
If you used Start > Settings > Administrative Tools > Computer Management > Storage > Disk Management, the disk must be visible to Windows, but NOT available as a C:, D:, E: (or any other) disk.
From that point on, there are three simple steps:
1) Answer the question: which direct accessed storage or raw logical volume or LUN are you using dedicated to ASM?
2) After that, you install the ASM software from the database installation disks. Put it into it's own ORACLE_HOME, select ASM installation, and tell it which disks from the above step that you reserved for ASM. This will present all available raw disks from step 1 to let yuo create a disk group.
3) Finally, from a database software ORACLE_HOME, run DBCA and tell it to use ASM as the storage for the database.

Create ASM Failure Group via dbca

Similar Messages

Maybe you are looking for