ASM - Adding Disks and DiskGroups

I am quite eager to start using ASM on one of our test databases.
Using localconfig add, I have configured CSS, and am now using the dbca wizard to create an ASM instance and add disks and diskgroups.
I have reached the point in the wizard, where the wizard is showing no disk groups and we have to create new disk groups.
At this point I click "Create New" button, but in the "select member disks" it shows no disks to select. I though ASM can manage filesystems, disks and raw devices. Why is it not showing any disks here? There are plenty of disks when I do a df -h on the unix prompt. Shouldnt the disks available in the filesystem be available here?
I am asking this question knowing pretty well that it is probably the daftest question ever asked on this forum. Sorry for that!

Thanks.
I have defined the parameter ASM_DISKSTRING to a value of / (forward slash). I was hoping that this should enable disk discovery. The filesystems available on my server as checked through df -h are as follows.....
Filesystem_
/dev/md/dsk/d12
/proc
mnttab
fd
/dev/md/dsk/d32
swap
swap
/dev/md/dsk/d51
/dev/md/dsk/d52
/dev/md/dsk/d53
/dev/md/dsk/d54
/dev/md/dsk/d56
/dev/md/dsk/d55
/dev/md/dsk/d57
/dev/md/dsk/d71
/dev/md/dsk/d73
/dev/md/dsk/d72
/dev/md/dsk/d74
/dev/md/dsk/d75
/dev/md/dsk/d76
/dev/md/dsk/d77
/dev/md/dsk/d79
I tried giving the /dev/md/dsk path as well, but that does not seem to change anything either...
I tried both the above and also tried changing the disk discovery path in the wizard....
Nothing works.

Similar Messages

Adding ocrmirror and voting disk on another diskgroup 11gr2 RAC

Hi Gurus,
Can i add ocrmirror on another diskgroup(external redundancy) and voting disk(normal) on anotherdiskgroup (replace) in 11gr2 RAC while databases are up and running?

Hi
in Oracle 11gr2 voting disk are backed up automatically in the ocr part of any configuration change
Voting disk is automatically restored to any added voting disk
You can migrate voting fıska from non asm to asm without
Taking download cluster
To add a voting disk to asm
Crsctl replace votedisk +diskgroup
Ocrconfig -add +datagroup2
Oracle manage up to five redundant ocr locations
Hope this helps
Zekeriya Besiroglu
Http://zekeriyabesiroglu.blogspot.com

Adding disk to existing disk group in ASM on the windows 2003 server.

Guys,
Can someone please share some opinions of adding an extra disk to an existing disk group ( DG_FRA ) in ASM on a windows 2003 server ( like any issues when bringing db backup ). This is a production database and I want to be careful , so that I don't have any issues with the database. Existing DG_FRA is 550GB ( size of the image copy is 325GB ),recently we have been running heavy loads and this is filling up the archive logs and forcing us to take incremental backups couple of times before deleting the archive logs. As a result of this we decided to add an extra 200GB so that we don't have to do this backups frequently during the day. Storage is on EMC SAN and the database is in 11G.
Thanks for all your help.

There will not be any issues..
stamp the disk and then add the disk.
You can also follow this approach -
stamp the disk.
create a new group and then add a datafile in this new group for the existing tablespace.

ORA-15063: ASM discovered an insufficient number of disks for diskgroup

Hello DBAs,
I have encountered this problem. I am using storage vendor snapshot capability. On my first node, I have 2 disks for ASM diskgroups. ORCL:DATA belongs to DATA diskgroup and ORCL:FLASH belongs to FLASH diskgroup. After making the snapshots of these two disks, I mapped them to my second host which already has ASM instance. I ran /etc/init.d/oracleasm scandisk and listdisks I see two disks. But when I start up ASM instance I get this error:
SQL> startup
ASM instance started
Total System Global Area 130023424 bytes
Fixed Size 2019032 bytes
Variable Size 102838568 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "FLASH"
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"
Of course, I have the asm_diskstring and asm_diskgroups parameter set in my init+ASM.ora file. The ASM version is identical across both hosts. I guess my question would be, is it possible to do this? Do I need to re-create the ASM disks using /etc/init.d/oracleasm? Any help is much appreciated.
Thanks,
TD

What is your configuration?
If you have AIX and EMC san, then refer to this metalink note: 467702.1
In my case, it was HP-UX and HP san EVA8200. But our problem was two different disks were presented to the two nodes, with same names by the unix admin/san admin guys.
Before they could figure out the problem, I had done a lot of research for few days to figure this out. Another problem I noticed in some cases was improper permissions. Either the db software owner didn't have permissions to the asm disks, or if the owner of both software was same, then the actual permissions/ownership of the shared raw devices was different on the two nodes.
Hope this helps. And I will appreciate once you fix the problem if you can also update this forum with your solution. That will help the community in future.
Thanks

ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DB

Dear All,
we are moved our storage from hitachi to EMC . after come to emc no issue.
But few day before we are try to use old hitachi storage for our T&D,the same storage mounted in new server.
After that we are try to start the asm but it disk group not mounted .
It show following error....
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DB01"
1) we are checked the 52 raw devices have oracle:dba permission we are verified.
2) all raw device can be viewed in v$asm_disk and state is normal.
3) we are tried asm_diskstring=* also
4) even it show same error.
1) My doubt is the asm meta data may be not correct how can i verifiy the the asm metadata and how can i resolve this asm error.
2) If i drop this asm diskgroup and recreate in same name and add all 52 disk to the group the data will be loss or not?
Thanks&regards
SS.vijaibabu

1) My doubt is the asm meta data may be not correct how can i verifiy the the asm metadata and how can i resolve this asm error.Asm metadata will get stored in asm_disks it's self. we cannot retrieve metadata unless you mount the diskgroup.Most probably these would be permission related of disks.
any pointings to alert log Errors of this operation.
>2) If i drop this asm diskgroup and recreate in same name and add all 52 disk to the group the data will be loss or not?
The header status of disks changes to FORMER ,once we fire drop on it.we cannot get back the data becase asm will format the disk after dropping.

ASM best practices question: minimum disks per diskgroup

Our ASM storage is on a SAN, so all disks are external redundancy. Since the SAN is striping before it is presented to the host, is there a minimum number of disks per diskgroup that is recommended? We have a vendor that recommends a minimum of 8 disks per diskgroup and I'm trying to validate that. TIA...

user11984434 wrote:
Our ASM storage is on a SAN, so all disks are external redundancy. Since the SAN is striping before it is presented to the host, is there a minimum number of disks per diskgroup that is recommended? We have a vendor that recommends a minimum of 8 disks per diskgroup and I'm trying to validate that. TIA...AFAIK, there is no such criterion for minimum disks in diskgroup. Vendor might have suggested it depending on size of database or may be some grouping of tablespaces per diskgroup etc.
Regards
Rajesh

ASM discovered an insufficient number of disks for diskgroup

Running RH4U3 and Oracle 10gr2
Every time I reboot my system, the minor number changed and i can't startup the ASM instance. Does any one know why this is happening? Any advise would be appreciated.
the minor number was 4 and 5, now after reboot i got::
# ls -l /dev/oracleasm/disks
total 0
brw-rw---- 1 ora dba 253, 4 Feb 21 10:10 VOL1
brw-rw---- 1 ora dba 8, 65 Feb 21 10:10 VOL2
I can't startup my ASM instance:
$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Feb 21 10:13:03 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ASM instance started
Total System Global Area 83886080 bytes
Fixed Size 1217836 bytes
Variable Size 57502420 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "OARCH"
y ASM instance:

I have no problem reading the disks.
$ dd if=/dev/oracleasm/disks/VOL1 of=/dev/null
485336+0 records in
485336+0 records out
$ dd if=/dev/oracleasm/disks/VOL2 of=/dev/null
741760+0 records in
741760+0 records out

I installed google chrome and added it to my applications folder and it works but my desktop still has the icon of the chrome volume/disk and when i right click it gives an option to eject but it will not delete how can I get rid of it?

I installed google chrome and added it to my applications folder and it works but my desktop still has the icon of the chrome volume/disk and when i right click it gives an option to eject but it will not delete how can I get rid of it?

Drag it to the trash icon in your dock. This is a disk image, and you need to "eject" it, to get rid of it.

Backup and Restore OCR,Voting Disk and ASM Disks in new SAN-10g RAC

Dear Friends,
I am using 10g R2 RAC serup on Linux
My OCR,Voting Disk and ASM Disk for DBF Files are on a SAN box
Now i am reorganising SAN by scrapping the entire SAN and cretaing new LUN's (It's a must)
so pleae let me know
1) how do i take backup of OCR and Voting Disk from existing SAN and how do i restore it in new LUN's after SAN reorganisation
2) how do i take backup of existing Database's from existing SAN and how do i restore it in new LUN's after SAN reorganisation.
I will be doing it in Planned downtime only
Regards,
DB

For step 1 you should following metalink doc.
For step 2 here is simple backup command script.
I have done this in windows for you.
D:\app\ranjit\product\11.2.0\dbhome_1\BIN>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Feb 8 21:48:47 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1299593730)
RMAN> run
+{+
allocate channel c1 device type disk format 'D:\app\ranjit\rman\%U';
allocate channel c2 device type disk format 'D:\app\ranjit\rman\%U';
backup database;
backup current controlfile format 'D:\app\ranjit\rman\%U';
+}+
Regards

New added disk in vm virtual box not shown in solaris

hi,
I have added new disk in VM virtual box to use it for asm, using storage tree in Vm virtual box i have added two new disks but after that when i start my OS (solaris 10) and use format command it only shows my one disk not the added disk which i add in storage. Any idea why the new added disks are not shown .
Thanks
Zeeshan

Navigate to the repository tab in OVMM and right-click on the storage repo, where you created/copied the vm disk image file. From the pop-up menu choose refresh repository.
That should scan you repository and make the new disk visible on OVMM.

ASM instance wont mount diskgroup..

HI, I have 10g release 2 installed on CENTOS 4.4, I use ASM striping with with 4 raw disks.
I had a system crash due to a power failure and now the the ASM wont mount the diskgroup.
export $ORACLE_HOME=+ASM
SQL> startup mount;
ASM instance started
Total System Global Area 130023424 bytes
Fixed Size 2071000 bytes
Variable Size 102786600 bytes
ASM Cache 25165824 bytes
ORA-15110: no diskgroups mounted
SQL> alter diskgroup RESEARCH1 mount;
alter diskgroup RESEARCH1 mount
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup
"RESEARCH1"
now when I use /etc/init.d/oracleasm listdisks I can see all my disks:
DISK1
DISK2
DISK3
DISK4
then i tried to change asm_diskstring to point the mounting point, here is my ora file:
*.asm_diskgroups='RESEARCH1'
+ASM.asm_diskgroups='RESEARCH1' #Manual Dismount
*.asm_diskstring='/dev/oracleasm/disks'
*.background_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/bdump'
*.core_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/cdump'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'
*.user_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/udump'
any ideas?
Thanks
Assaf

Hi,
by oracleasm lib utility you can configure as below
# /etc/init.d/oracleasm configure
Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Scanning system for ASM disks: [ OK ]
# /etc/init.d/oracleasm enable
Thanks

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?

Alert log: failed to establish dependency between database and diskgroup

Hi, I have a database 11.2.0 with ASM. When I startup an instance I see this error in alert log:
ERROR: failed to establish dependency between database SPBUFOR and diskgroup resource ora.SPBUFOR_FLASH.dg
SPBUFOR_FLASH is a diskgroup where a flash recovery area is located.
Database is opened cleanly but I need to know that everything works fine.
How can I resolve this issue ?

ASM ALERT LOG:
Wed Oct 05 15:35:12 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.2.0/grid/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =0
LICENSE_MAX_USERS = 0
SYS auditing is disabled
NOTE: Volume support enabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Automatic Storage Management option.
Using parameter settings in server-side spfile +CSA_DATA/asm/asmparameterfile/registry.253.758208241
System parameters with non-default values:
large_pool_size = 12M
instance_type = "asm"
remote_login_passwordfile= "EXCLUSIVE"
asm_diskgroups = "CSA_FLASH"
asm_diskgroups = "SPBUFOR_DATA"
asm_diskgroups = "SPBUFOR_FLASH"
asm_power_limit = 1
diagnostic_dest = "/u01/app/oracle"
Wed Oct 05 15:35:13 2011
PMON started with pid=2, OS id=24108
Wed Oct 05 15:35:14 2011
VKTM started with pid=3, OS id=24112 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Oct 05 15:35:14 2011
GEN0 started with pid=4, OS id=24118
Wed Oct 05 15:35:14 2011
DIAG started with pid=5, OS id=24122
Wed Oct 05 15:35:14 2011
PSP0 started with pid=6, OS id=24127
Wed Oct 05 15:35:14 2011
DIA0 started with pid=7, OS id=24131
Wed Oct 05 15:35:14 2011
MMAN started with pid=8, OS id=24135
Wed Oct 05 15:35:14 2011
DBW0 started with pid=9, OS id=24139
Wed Oct 05 15:35:14 2011
LGWR started with pid=10, OS id=24143
Wed Oct 05 15:35:14 2011
CKPT started with pid=11, OS id=24148
Wed Oct 05 15:35:14 2011
SMON started with pid=12, OS id=24157
Wed Oct 05 15:35:14 2011
RBAL started with pid=13, OS id=24163
Wed Oct 05 15:35:14 2011
GMON started with pid=14, OS id=24173
Wed Oct 05 15:35:14 2011
MMON started with pid=15, OS id=24177
Wed Oct 05 15:35:14 2011
MMNL started with pid=16, OS id=24181
ORACLE_BASE from environment = /u01/app/oracle
Wed Oct 05 15:35:15 2011
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: Diskgroups listed in ASM_DISKGROUPS are
CSA_FLASH
SPBUFOR_DATA
SPBUFOR_FLASH
Diskgroup with spfile:CSA_DATA
NOTE: cache registered group CSA_DATA number=1 incarn=0x75fe76df
NOTE: cache began mount (first) of group CSA_DATA number=1 incarn=0x75fe76df
NOTE: cache registered group CSA_FLASH number=2 incarn=0x760e76e0
NOTE: cache began mount (first) of group CSA_FLASH number=2 incarn=0x760e76e0
NOTE: cache registered group SPBUFOR_DATA number=3 incarn=0x760e76e1
NOTE: cache began mount (first) of group SPBUFOR_DATA number=3 incarn=0x760e76e1
NOTE: cache registered group SPBUFOR_FLASH number=4 incarn=0x761e76e2
NOTE: cache began mount (first) of group SPBUFOR_FLASH number=4 incarn=0x761e76e2
NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
NOTE: Assigning number (1,0) to disk (ORCL:CSA_D1)
NOTE: Assigning number (1,1) to disk (ORCL:CSA_D2)
NOTE: Assigning number (2,0) to disk (ORCL:CSA_F1)
NOTE: Assigning number (2,1) to disk (ORCL:CSA_F2)
NOTE: Assigning number (3,0) to disk (ORCL:SPBUFOR_D1)
NOTE: Assigning number (3,1) to disk (ORCL:SPBUFOR_D2)
NOTE: Assigning number (3,2) to disk (ORCL:SPBUFOR_D3)
NOTE: Assigning number (4,0) to disk (ORCL:SPBUFOR_F1)
NOTE: Assigning number (4,1) to disk (ORCL:SPBUFOR_F2)
NOTE: start heartbeating (grp 1)
kfdp_query(CSA_DATA): 6
kfdp_queryBg(): 6
NOTE: cache opening disk 0 of grp 1: CSA_D1 label:CSA_D1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 1: CSA_D2 label:CSA_D2
NOTE: cache mounting (first) external redundancy group 1/0x75FE76DF (CSA_DATA)
NOTE: cache recovered group 1 to fcn 0.25573
NOTE: LGWR attempting to mount thread 1 for diskgroup 1 (CSA_DATA)
NOTE: LGWR found thread 1 closed at ABA 4.2486
NOTE: LGWR mounted thread 1 for diskgroup 1 (CSA_DATA)
NOTE: LGWR opening thread 1 at fcn 0.25573 ABA 5.2487
NOTE: cache mounting group 1/0x75FE76DF (CSA_DATA) succeeded
NOTE: cache ending mount (success) of group CSA_DATA number=1 incarn=0x75fe76df
NOTE: start heartbeating (grp 2)
kfdp_query(CSA_FLASH): 8
kfdp_queryBg(): 8
NOTE: cache opening disk 0 of grp 2: CSA_F1 label:CSA_F1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 2: CSA_F2 label:CSA_F2
NOTE: cache mounting (first) external redundancy group 2/0x760E76E0 (CSA_FLASH)
NOTE: cache recovered group 2 to fcn 0.49881
NOTE: LGWR attempting to mount thread 1 for diskgroup 2 (CSA_FLASH)
NOTE: LGWR found thread 1 closed at ABA 3.5793
NOTE: LGWR mounted thread 1 for diskgroup 2 (CSA_FLASH)
NOTE: LGWR opening thread 1 at fcn 0.49881 ABA 4.5794
NOTE: cache mounting group 2/0x760E76E0 (CSA_FLASH) succeeded
NOTE: cache ending mount (success) of group CSA_FLASH number=2 incarn=0x760e76e0
NOTE: start heartbeating (grp 3)
kfdp_query(SPBUFOR_DATA): 10
kfdp_queryBg(): 10
NOTE: cache opening disk 0 of grp 3: SPBUFOR_D1 label:SPBUFOR_D1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 3: SPBUFOR_D2 label:SPBUFOR_D2
NOTE: cache opening disk 2 of grp 3: SPBUFOR_D3 label:SPBUFOR_D3
NOTE: cache mounting (first) external redundancy group 3/0x760E76E1 (SPBUFOR_DATA)
NOTE: cache recovered group 3 to fcn 0.317867
NOTE: LGWR attempting to mount thread 1 for diskgroup 3 (SPBUFOR_DATA)
NOTE: LGWR found thread 1 closed at ABA 3.8570
NOTE: LGWR mounted thread 1 for diskgroup 3 (SPBUFOR_DATA)
NOTE: LGWR opening thread 1 at fcn 0.317867 ABA 4.8571
NOTE: cache mounting group 3/0x760E76E1 (SPBUFOR_DATA) succeeded
NOTE: cache ending mount (success) of group SPBUFOR_DATA number=3 incarn=0x760e76e1
NOTE: start heartbeating (grp 4)
kfdp_query(SPBUFOR_FLASH): 12
kfdp_queryBg(): 12
NOTE: cache opening disk 0 of grp 4: SPBUFOR_F1 label:SPBUFOR_F1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 4: SPBUFOR_F2 label:SPBUFOR_F2
NOTE: cache mounting (first) external redundancy group 4/0x761E76E2 (SPBUFOR_FLASH)
NOTE: cache recovered group 4 to fcn 0.16114
NOTE: LGWR attempting to mount thread 1 for diskgroup 4 (SPBUFOR_FLASH)
NOTE: LGWR found thread 1 closed at ABA 2.1922
NOTE: LGWR mounted thread 1 for diskgroup 4 (SPBUFOR_FLASH)
NOTE: LGWR opening thread 1 at fcn 0.16114 ABA 3.1923
NOTE: cache mounting group 4/0x761E76E2 (SPBUFOR_FLASH) succeeded
NOTE: cache ending mount (success) of group SPBUFOR_FLASH number=4 incarn=0x761e76e2
kfdp_query(CSA_DATA): 13
kfdp_queryBg(): 13
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 1
SUCCESS: diskgroup CSA_DATA was mounted
kfdp_query(CSA_FLASH): 14
kfdp_queryBg(): 14
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 2
SUCCESS: diskgroup CSA_FLASH was mounted
kfdp_query(SPBUFOR_DATA): 15
kfdp_queryBg(): 15
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 3
SUCCESS: diskgroup SPBUFOR_DATA was mounted
kfdp_query(SPBUFOR_FLASH): 16
kfdp_queryBg(): 16
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 4
SUCCESS: diskgroup SPBUFOR_FLASH was mounted
SUCCESS: ALTER DISKGROUP ALL MOUNT
SQL> ALTER DISKGROUP ALL ENABLE VOLUME ALL
SUCCESS: ALTER DISKGROUP ALL ENABLE VOLUME ALL
NOTE: diskgroup resource ora.CSA_DATA.dg is online
NOTE: diskgroup resource ora.CSA_FLASH.dg is online
NOTE: diskgroup resource ora.SPBUFOR_DATA.dg is online
NOTE: diskgroup resource ora.SPBUFOR_FLASH.dg is online
Wed Oct 05 15:35:44 2011
Starting background process ASMB
Wed Oct 05 15:35:44 2011
ASMB started with pid=18, OS id=24330
Thu Oct 06 11:48:19 2011
SQL> alter diskgroup SPBUFOR_DATA check all
NOTE: starting check of diskgroup SPBUFOR_DATA
kfdp_checkDsk(): 17
kfdp_checkDsk(): 18
Thu Oct 06 11:48:30 2011
kfdp_checkDsk(): 19
SUCCESS: check of diskgroup SPBUFOR_DATA found no errors
SUCCESS: alter diskgroup SPBUFOR_DATA check all
Thu Oct 06 11:48:56 2011
SQL> alter diskgroup SPBUFOR_FLASH check all
NOTE: starting check of diskgroup SPBUFOR_FLASH
kfdp_checkDsk(): 20
kfdp_checkDsk(): 21
SUCCESS: check of diskgroup SPBUFOR_FLASH found no errors
SUCCESS: alter diskgroup SPBUFOR_FLASH check all

How ASM Manages Disk Failures

Hi,
Was going through Oracle ASM document and came across this topic, need some clarification on this please.
"The disks are first taken offline and then automatically dropped. In this case, the disk group remains mounted and serviceable. In addition, because of mirroring, all of the disk group data remains accessible. After the disk drop operation, Oracle ASM performs a rebalance to restore full redundancy for the data on the failed disks". -- What does this mean?
Thanks

Simple example.
Single normal redundancy diskgroup DATA1 with 2 failgroups called MIRROR1 and MIRROR2. Each failgroup has 3 x disks (let's say 512GB).
Disk 2 in failgroup MIRROR1 fails. The MIRROR1 failgroup is not available as a result. DB operations continue unaware of the problem as MIRROR2 is online and working fine.
The dba cannot fix disk 2 within the meantime for repair period of ASM. ASM forces disk 2 out the MIRROR1 failgroup by force dropping it. MIRROR1 has now 2 disk remaining.
ASM starts a rebalance process to stripe the contents of the MIRROR1 failgroup across 2 disks - as oppose to 3 disks. If the space in use fits on 2 disks the rebalance operation will succeed. MIRROR1 will become online and available. But it will only be able to carry 1TB of data, as oppose to MIRROR2 with it 3 disks and 1.5TB capacity.
If the space used cannot be striped across the remaining disks in MIRROR1, the rebalance will fail due to insufficient capacity and the failgroup will remain offline.
In either scenario, the recommended action is to add a new 512GB disk to MIRROR1, reverting it back to a 3 disk failgroup, and then rebalance the failgroup.

Can multiple ASM instnace have same diskgroup name

Hi all,
suppose i have two asm instance asm1 and asm 2 running on same node. can i create diskgroup with same name on both asm instances .
Thanks.

First of all, I don't think you should run more than one asm instance on a single node. See Multiple ASM Instances on single node and that for some more information on this.
Anyway, I don't see why you would not be able to create a diskgroup with the same name in both asm instances (as long as they use seperate disks). But that would only add to the confusion and I don't see a practical use for it.
Bjoern

ASM - Adding Disks and DiskGroups

Similar Messages

Maybe you are looking for