Basically it does a round-robin allocation (+ disk (LUN) size acquiring). It tries to avoid the hot spots by striping extents across different disks. But it can't say "uh-huh, we got a hot spot here let's try to move those things here and there". On 2/27/07, Don Seiler <don@xxxxxxxxx> wrote:
My understanding is that ASM will also shift data around to avoid the "hot block" scenario, avoiding I/O contention. It wasn't explicitly stated in the passage I pasted, hopefully my understanding is correct. Don.
-- Alexander Fatkulin, Senior Oracle DBA -- http://www.freelists.org/webpage/oracle-l