on top of what Raj wrote - there can as well be dependencies coming from the
use of the disk group.
For example, Redo Block size is always directly derived from the disk's LBA
size. If you migrate to another one, you may run into another subset of
Martin Klier // Performing Databases GmbH
Managing Partner // Senior DB Consultant
Oracle ACE Director
martin.klier@xxxxxxxxxxxxxxxxx // https://www.performing-databases.com ;
Von: "Rajesh Aialavajjala" <r.aialavajjala@xxxxxxxxx>
CC: "Oracle-L Freelists" <oracle-l@xxxxxxxxxxxxx>
Gesendet: Mittwoch, 13. Oktober 2021 02:16:28
Betreff: Re: ASM adding disk with different sector size
To the best of my understanding - ASM does not permit mixed sector sizes in a
single disk group - so I presume that rules out the use of the 'removing the
old disks and rebalance as we go'
You didn't include the version of grid infrastructure/ASM that your
is running ... but this was not allowed in 12c...
12c --> [
In 19c and higher - there's the concept of logical_sector_sizes and
physical_sector_sizes but I am unsure of how that would fit into your
Additions, comments, corrections welcome (and I will gladly defer to the wiser
folks in this group)
On Tue, Oct 12, 2021 at 2:16 PM Sandra Becker < [
sbecker6925@xxxxxxxxx ] > wrote:
We need to move some databases off of their current storage, which is old
longer supported. The new disk will have a different sector size. Can we
a new diskgroup for the new storage and use it along with the old storage? If
possible, can we do the balancing and then start removing the old disks and
rebalance as we go? I'm not very familiar with ASM, so would appreciate some
guidance or pointing me to an appropriate document. I've been doing some
searches, but still not sure we can move the databases in this manner.