Re: Server Architecture
Date: Thu, 3 Jan 2008 08:21:35 -0600
That architecture has some advantages but with disadvanatges that others pointed out.
I used similar architecture for oracle ebusiness env for all non production instances. Because of frequent clones and being potentially on different patchsets, it made sense for me. Also it allowed for separation of duties along instances.
I wouldn't do it for production and not certainly for 100 databases.
I think virtualization can be used, but I believe it has licensing impact
On 1/2/08, Satheesh Babu.S <satheeshbabu.s_at_gmail.com> wrote:
> We have been proposed with following architecture by our consultant. I need
> your expert opinion on this.
> Assume a server got 5 database and all the databases running in same oracle
> version and patchset.
> They are proposing to create 5 unix account. Each unix account will have one
> oracle binaries and corresponding oracle DB. Apart from that each unix
> account will have dedicated mountpoints. In broader sense each unix account
> will be logically considered as one server.
> I am slightly worried about this architecture. Because when this
> architecture goes to production, the impact it will have on maintenace going
> to be huge. Assuming i am having minimum 100 db in production( ours is a
> very large shop) and if i need to apply one patch to all these servers going
> to kill us. Secondly, will there be a impact on licensing. I don't think so,
> but like to check it up with you guys. I know it has got some advantage too.
> But is this approach is suitable for large shop like us?
> Satheesh Babu.S
-- Sent from Gmail for mobile | mobile.google.com -- http://www.freelists.org/webpage/oracle-lReceived on Thu Jan 03 2008 - 08:21:35 CST