Sure, understood. Virtualization is pretty cool and has its place, but it has to be used wisely. High stress mission-critical environments that I would not hesitate to put on any other vendors hardware or OS, including RH Linux, IMO should never be put under VMware...performance is so bad. My findings are that production databases just don't belong on VMware unless the application is really small. You really hit the nail dead-on- its got to be low stress (i.e. light activity). Although performance is my big complaint, reliability seems to be fine. ________________________________ From: Jared Still [mailto:jkstill@xxxxxxxxx] Sent: Wednesday, December 31, 2008 1:06 PM To: Crisler, Jon Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: db_recovery_file_dest_size On Wed, Dec 31, 2008 at 9:05 AM, Crisler, Jon <Jon.Crisler@xxxxxxx> wrote: Jared, I cringed when I saw your sentence advocating virtualization to address this problem. In my experience putting Oracle on a virtual server is a cure worse than the disease, at least where Xen and VMware are concerned. They are great for test / dev / qa systems, as long as the performance equation is ignored :-) Come to think if it, this applies to MS SQL Server and MySQL as well. If performance is important, or at least consistent performance is required, virtualization with Vmware or Xen supporting databases on either Linux or Windows has been a colossal disappointment for me. Sorry Jon, I didn't really mean to be an advocate for virtualization of Oracle datababases. I don't really care for it too much myself, except in limited circumstances. eg. I am using a virtual linux server for a replicated OID environment. This is a very low stress application, (db names resolution only) so no problems there. The parameter under discussion seemed that it may well lend itself to use in virtual environments. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist