Hi=20 >- How is extent management handled in ASM databases? I believe the ASM >instance maps the physical drive and extents, but does this take >extent management sizing away from the dba? All the ASM online and >book examples I am finding are pretty generic with regards to the meat >of creating tablespaces/objects inside the ASM diskgroups. I assume it >is all local segment and space managed. >- How would extent/object sizing conversions to ASM (adding ASM to an >existing instance or export/import to a new ASM) be handled? From a database point of view there's no difference with the storage = options. Only the file names are different. Of course you would probably use = OMF...=20 >- How does ASM handle blocksizes? I haven't seen an example where >someone tries to use different blocksizes inside an ASM diskgroup. I >suppose it becomes irrelevant when using raw devices. Yes, no problem at all.=20 >- Are there any quirks using the external redundancy clause? I >wouldn't think so, but I wonder how Oracle would "rebalance" inside >the diskgroup with external redundancy.. or is rebalancing "off" when >external redundancy is specified, since some volume managers give >sysadmins the ability to find/move hot disks? Rebalancing always work. This is independent from the redundancy.=20 Chris -- //www.freelists.org/webpage/oracle-l