RE: Server Architecture

Well, that can get messy with a) remembering what databases are in what
homes, and b) naming conventions and the like.  It's useful to be able
to say, "I know what the home is purely by virtue of the instance name"
or something similar.  Or if someone moves a database over and another
DBA doesn't get the memo, and it gets started out of the wrong home or
what have you.  Badness can result.

 

Thanks,

Matt

 

________________________________

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Dan Norris
Sent: Thursday, January 03, 2008 11:26 AM
To: tanel.poder.003@xxxxxxx; Oracle L
Subject: Re: Server Architecture

 

If they're all on the same patch level today, why introduce all the
ORACLE_HOMEs today? Personally, I'd keep them all on the same
ORACLE_HOME now and when one wants to patch and the others aren't ready,
spin up a new ORACLE_HOME, patch it, then migrate the DB in question to
use the new ORACLE_HOME at that point. That way, if you don't run into
patching conflicts, you'll never need the extra ORACLE_HOMEs. Is there
something wrong with my logic?

Dan

Other related posts: