Professional Documents
Culture Documents
APPLIES TO:
[HTTPS://WWW.BLOGGER.COM/NULL] PURPOSE
This document is a discussion of a few 12C ASM new features with examples:
1. Failgroup_repair_time
3. Estimate Work
4. V$ASM_OPERATION view
[HTTPS://WWW.BLOGGER.COM/NULL] DETAILS
1. FAILGROUP_REPAIR_TIME
For versions <= 11g, we had disk_repair_time, from 12C onwards we have failgroup_repair_time at the ASM level. Because
failure group outages are more likely to be transient in nature and because replacing all the disks in a failure group is a much
more expensive operation than replacing a single disk, it would typically make sense for failure groups to have a larger repair
time to ensure that all the disks do not get dropped automatically in the event of a failure group outage.
By default, the value of this diskgroup level attribute is 24Hours. To set this attribute at ASM diskgroup level, one must set
compatible.asm and compatible.rdbms greater than or equal to 11.1.0.0.
Test Case:
## Newly created diskgroup,
## Validated both attribute of this diskgroup,it remained same to support backward compatibilities.
http://sateeshv-dbainfo.blogspot.in/2017/06/12c-asm-new-feature.html 1/5
9/19/2017 12C ASM New feature
NAME COMPATIBILITY DATABASE_COMPATIBILITY
4 failgroup_repair_time
3H
If an ASM disk becomes offline and cannot be repaired, administrators need the ability to replace the disk. In versions of ASM
prior to 12c, there was no replace command. Rather, administrators had to drop the faulty disk and then add a new one back
into the disk group which causes an ASM level rebalance. Depending on multiple internal and external factors, reblance can be
time consuming.
In 12c, ASM allows DBAs to simply replace an offline disk using one fast and efficient operation. There is no need for any
additional reorganization or rebalancing across the rest of the disk group.
ASM diskgroup level attribute compatible.asm should be of 12.1.0.0 for this feature
Replacing disk should bad in true sense , ASM will not replace online disk.
http://sateeshv-dbainfo.blogspot.in/2017/06/12c-asm-new-feature.html 2/5
9/19/2017 12C ASM New feature
The replacement disk takes the same name as the original disk and becomes part of the same failure group as the original
disk.
Then replacing good disk should be sized equal or greater than replacing bad disk.Else replace will fail.
Test case:
## Tried to replace a disk with compatible.asm 10.1.0.0
## To replace this disk ,for testing purpose ,change the permission of that disk .
http://sateeshv-dbainfo.blogspot.in/2017/06/12c-asm-new-feature.html 3/5
9/19/2017 12C ASM New feature
TEST_FAILGROUP_0001 /dev/sdh2 2565
TEST_FAILGROUP_0002 /dev/sdg1
2165 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
TEST_FAILGROUP_0000 /dev/sde2 2565
## Added disk was lager in size of original disk.
But at ASM level only same size allocated as old bad disk.
## Simulate similar type of issue and tried to replace with less sized disk than bad disk.
It did not allow replacement
3. Estimate Work
Before 12C, the only way to know how long an expensive operation like disk add/drop at diskgroup level was to actually perform
the operation, so there was no way to predict before-hand how much time this would take.
In 12c ASM, a more detailed and more accurate work plan is created at the beginning of each rebalance operation. In addition,
DBAs can separately generate and view the work plan before performing a rebalance operation. This allows DBA to better plan
and execute various changes such as adding storage, removing storage or moving between different storage systems.
DBAs can generate the work plan using the ESTIMATE WORK command.
Querying from V$ASM_ESTIMATE view give an idea of required time of that operation based on current workload on the
system. This feature allows DBAs to consider system load implications while planning an operation before actually taxing the
system.
Note: be sure to give the correct disk name, otherwise this estimation will fail
http://sateeshv-dbainfo.blogspot.in/2017/06/12c-asm-new-feature.html 4/5
9/19/2017 12C ASM New feature
ORA-15054: disk "TEST_FAILGROUP_0005" does not exist in diskgroup
"TEST_FAILGROUP"
4. V$ASM_OPEARATION view
From version 11g onwards, we have a compact phase while rebalancing. While this phase used to run at ASM level for a
diskgroup, we cannot estimate compact phase timing approximately.
We used to see EST_MINUTES is 0. At the same time we were also not able to track resync operations separately.
In 12C, we can view these phases separately from v$asm_operation, giving a better idea about on-going operation based on
current utilization of the system.
[https://www.blogger.com/null] [https://www.blogger.com/null] [https://www.blogger.com/null] [https://www.blogger.com/null]
RESYNC RUN 1
REBALANCE WAIT 20
COMPACT WAIT 2
Things to Check in ASM When Replacing an ONLINE disk from Exadata Storage Cell (Doc ID
1326611.1)
Note---> This informationmation taken from oracle metalink. all copy rights oracle only.
0 Add a comment
http://sateeshv-dbainfo.blogspot.in/2017/06/12c-asm-new-feature.html 5/5