Hi Dan, We've been an ASM shop since we moved to 10.2 several years ago, and are quite comfortable with it. We started (relatively) small, with a few 100-200GB databases. Recently, our content store re-architecture means that we've got an 11.2 database that's about 10TB (and growing) on ASM. Overall, I'm pleased with the combination of ASM, bigfile tablespaces, and OMF. It means that tablespace level monitoring is a thing of the past. We have everything in ASM, OCR, data, redo, flashback (which is where we write archivelogs). I just monitor space usage in the disk groups, and, when I start running low, the storage admin provides another chunk of raw disk, which I add to the diskgroup, and I'm good to go. Each tablespace grows at its own rate, allocating space from the diskgroup. Depending on the tablespace, you may want to set limits on specific tablespaces, but, for our big tablespace, it's just set to unlimited, and I add space to the diskgroup as needed. Overall, I think ASM is a good thing. -Mark -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Daniel W. Fink Sent: Friday, October 22, 2010 10:10 AM To: oracle-l Subject: Large ASM installation We have a customer that is looking at ASM to handle their databases, the total planned is about 8TB for a single ASM instance. Has anyone on the list worked on a large (5+TB) ASM system? What have been the pros and cons versus a regular LVM and storage? If you had the chance to go back to the decision time, would you make the same decision and why? I'm not needing nitty gritty details right now, more of a high level decision making view. Regards, Daniel Fink -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l