RE: Server Architecture

From: Bobak, Mark <>
Date: Thu, 3 Jan 2008 13:11:22 -0500
Message-ID: <>

Doesn't the oraenv script provide the knowledge of "what the home is purely by virtue of the instance name"?  

Just do:

. oraenv

At the ORACLE_SID = prompt, enter the sid you want, and you (should be) guaranteed the correct ORACLE_HOME, right?  


Mark J. Bobak
Senior Database Administrator, System & Product Technologies
789 E. Eisenhower, Parkway, P.O. Box 1346
Ann Arbor MI 48106-1346
+1.734.997.4059  or +1.800.521.0600 x 4059 <> <> <> 

ProQuest...Start here. 



[] On Behalf Of Matthew Zito
Sent: Thursday, January 03, 2008 12:38 PM To:;; Oracle L Subject: 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:
[] On Behalf Of Dan Norris
Sent: Thursday, January 03, 2008 11:26 AM To:; 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 --
Received on Thu Jan 03 2008 - 12:11:22 CST

Original text of this message