Re: Oracle installation on Local disk vs. SAN
- From: David Mann <dmann99@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Fri, 15 May 2009 10:19:14 -0400
In one of our data centers my group supports 250+ databases that run off of
18 shared Oracle homes (mix of 10g and 11g).
With regards to patching shared ORACLE_HOMES - yes it would definitely be
painful to try to get dozens of databases upgraded at the same time. So we
don't even try. Our rule is once a Home is set up and databases are using
it, we never touch it again until all databases are migrated off of it.
If we need to patch we install a new set of binaries and apply needed
patches, then schedule each upgrade each database individually and point
them at the new home. If we get a request for a database that requires a
home with a different set of patches than we already have available we do
the fresh install+patches, then set up the new database.
Some apps (Cognos, Informatica, streams, etc) are so dependent on a specific
mix of patches that they just end up getting their own home by default. We
also have a lot of lightweight apps that work just fine with current
terminal releases of 10g and 11g.
The biggest con for us is keeping everything organized. We keep a
configuration database with info about database/home usage. It is critical
that we reviewthis info before planning any changes to the environment.
The biggest benefit is that we also have datafiles on attached storage just
like the homes. If a server goes down for some reason we can attach the
storage to one of our other machines and start the database just by updating
a few symbolic links.
-Dave
--
Dave Mann
www.brainio.us
www.ba6.us - Database Stuff - http://www.ba6.us/rss.xml
Other related posts:
