We have two physical servers (2 Global Zones) running Solaris 10 and Veritas Cluster Server. Each server runs Solaris containers with about 5 databases. Our databases are multi-tenant. Downside is that when the server fails, all databases running on server fails with it. Good in theory, bad in practice. Michael Dinh NOTICE OF CONFIDENTIALITY - This material is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. BE FURTHER ADVISED THAT THIS EMAIL MAY CONTAIN PROTECTED HEALTH INFORMATION (PHI). BY ACCEPTING THIS MESSAGE, YOU ACKNOWLEDGE THE FOREGOING, AND AGREE AS FOLLOWS: YOU AGREE TO NOT DISCLOSE TO ANY THIRD PARTY ANY PHI CONTAINED HEREIN, EXCEPT AS EXPRESSLY PERMITTED AND ONLY TO THE EXTENT NECESSARY TO PERFORM YOUR OBLIGATIONS RELATING TO THE RECEIPT OF THIS MESSAGE. If the reader of this email (and attachments) is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. Please notify the sender of the error and delete the e-mail you received. Thank you. From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Sandra Becker Sent: Thursday, October 28, 2010 7:21 AM To: ORACLE-L Subject: Re: Single server vs multiple servers for multiple databases We started with a single LPAR for all our oracle databases. About 6 months ago we added a second LPAR. We also set up seperate VMs for each database. We did not split our application between databases. All production apps are in the same database. That VM has the highest priority. We also instituted some resource limits on users in the dev and qa databases to help mitigate issues with runaway processes from one VM affecting the other VMs. It has worked out well for us but took us about 4 months to tweak priorities and limits appropriately. -- Sandy Transzap, Inc.