Hi Qaiser, Many thanks for the answer ... if I understand you correctly you apply storage patches 2x per year, right? 80 consolidated databases on a half rack ... impressive. In context of this, what is average CPU and peak CPU utilization on each database node? I assume you apply i.e. test storage patches on test system before going productive ... did you encountered a case where patch apply failed? If yes, what was a reason? What is your fallback (rollback) scenario in case of patch failure on production system? How accurate do you find instructions & docs on Metalink describing storage patch apply procedure? Many thanks, goran On Wed, Nov 21, 2012 at 3:18 PM, Q A I S E R <qrasheed@xxxxxxxxx> wrote: > Goran, > > We are using Exadata for consolidation. We had a number of single instance > databases running on dedicated hardware. We have consolidated about 80 of > these databases into a half rack of Exadata. We recommend use of resource > management (DBRM/IORM) in a consolidated Exadata environment. > > Oracle releases Quarterly Bundle Patches (renamed to QDPE) for Exadata. We > apply one patch every 6 months, or two patches a year. Our applications > annoy afford down time. All patches are applied in a rolling fashion. It > takes a long time for rolling patches, but we are able to run our > production environment without any down time. Oracle offers Platinum > Support for Exadata. This includes one patch application by Oracle per > Quarter (4 patches per year). There is no cost, however you should meet > their pre-requisites. Your environment should be at a minimum patch release > to qualify for this service. > > Reference: > Database Machine and Exadata Storage Server 11g Release 2 (11.2) Supported > Versions [ID 888828.1] > > *Best practices for consolidation on Exadata* > > http://www.oracle.com/technetwork/database/features/availability/exadata-consolidation-522500.pdf > > Thanks, > --Qaiser > > On Nov 21, 2012, at 4:10 AM, goran bogdanovic <goran00@xxxxxxxxx> wrote: > > Hi list, > I have couple questions related to Exadata but first a little bit of > background story: > > I am considering different solutions for database consolidation as well as > increasing high availability of single systems in one step. > At present our production systems (OLTP & DWH) are running more or less as > isolated 'islands'. > Since the Data-Center is getting bigger & bigger so our DC as well > operational bill too. > Many systems don't really need dedicated HW to run on, so two or more of > them can be consolidated to run on e.g. one 2-node HA cluster with > sufficient CPU and IO resources to satisfy total needs of all databases > running on such high available 'consolidated platform'. > Oracle VM is not an option. > Lets put licensing topic aside for now. > > So, now back to original topic ;-) > > One of the options I am considering is Oracle Exadata. > I had a first (and short) workshop with people from Oracle which was more > let's say high-level presentation of Exadata. > The figures presenting 'power' of Exadata are impressive. > That's one side of picture. > > Topics which are still open for me are: > > 1. Patching/Upgrade of Exadata Storage Servers, Firmware, InfiBand switches > as well as other HW components > - how oft this need to be done? > - patching/upgrade in rolling fashion possible or not? > > > 2. Real life operational experience with Exadata > - I would be very grateful for any insights and experiences from list > members with Exadata experience i.e. faced bugs, problems & issues > > 3. Oracle sales presented a Turkcell as one which used Exadata as > consolidation platform ... if anyone on the list is working for them and > would be kind enough to share experience I would be very grateful. > > Many thanks in advance to anyone kind enough to tackle above topics. > > cheers, > goran > > > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l