Re: how much cpu on a database rac cluster
Date: Wed, 5 Sep 2012 11:00:53 +0300
Message-ID: <WED1s.26032$ck7.23510_at_uutiset.elisa.fi>
"Mladen Gogala" <gogala.mladen_at_gmail.com> wrote in message
news:pan.2012.09.05.06.59.35_at_gmail.com...
> On Wed, 05 Sep 2012 08:59:07 +0300, Jack wrote:
>
>> Well, I must say I totally disagree.
>>
>> One machine, one host -TEN INSTANCE
>>
>> That is called consolidating. (I am not talking about RAC).
>
> This must be a joke? Did I travel in time to April the 1st? 10 instances
> on a single machine is a "consolidation"? Why would anyone want to have
> 10 sets of background processes, 10 SGA areas and many wasted semaphores?
> Why is schema separation not enough? Are you coming from the MS SQL
> Server world? Such fascination with many databases is usually
> characteristic for the people with SQL Server background. While SQL
> Server is a great database, especially for DW purposes, its architecture
> is very much unlike Oracle, which prefers a single database.
>
>
>
> --
> Mladen Gogala
> http://mgogala.freehostia.com
And very other there is different instance for very good reason.
Management is also simple/better when having control for one business-system
per instance.
N:B. now talkin about non-RAC
With different instance you can better agree service time (shutdown) when only one plant/division/department to deal with, not the damn corporation.
And what you save with single instance, some bits. As clever saving as putting year into two digit, and get 2000-issues :) If separetes instances you can be sure no interfare with each system. Do security nor data involvent.
And no extra work to fit sepate systems into one instance, that saves money. And the last but not least, you have better control into separeted systems. Received on Wed Sep 05 2012 - 03:00:53 CDT