RE: the joy of version numbers

  • From: "Patterson, Joel" <jpatterson@xxxxxxxxxx>
  • To: "rjoralist2@xxxxxxxxxxxxxxxxxxxxx" <rjoralist2@xxxxxxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 24 May 2013 09:21:05 -0400

I agree,  I use /orasoft for software and branch through admin and work there 
-- although there is no cure for the "rm" issue pretty much where every you are.

The data is under /oradata -- actually on our Solaris containers the sysadmin 
creates mount points for each database ... /oradata/DB1  /oradata/DB2...

Why do you not just jump to the 5 digit version?  Since all upgrades or PSUs 
after 11202 are complete software installs, you end up with a new Oracle home 
-- allowing you to upgrade one database at a time assuming you have more than 
one using it.

(Caveat:  I might be missing something here as I have not yet moved forward 
with the next PSU)
/orasoft/app/oracle/11.2.0.3/...
Apply PSU
/orasoft/app/oracle/11.2.0.3/...???
 You would be overlaying on top of the exsiting home?  All DBs down.

Verses oracles new best practice -- out of line patching.   I think it is 
clearer and you don't have to query or check what version...  Each home is 
pretty small.
 /orasoft/app/oracle/11.2.0.3.0/...
Apply PSU
/orasoft/app/oracle/11.2.0.3.3/...???

I'm curious because this seems to be an item in the minority.


Joel Patterson
Database Administrator
904 928-2790



--
Joel Patterson
Sr. Database Administrator | Enterprise Integration
Phone: 904-928-2790 | Fax: 904-733-4916
http://www.entint.com/

http://www.entint.com/

http://www.facebook.com/pages/Enterprise-Integration/212351215444231 
http://twitter.com/#!/entint http://www.linkedin.com/company/18276?trk=tyah 
http://www.youtube.com/user/ValueofIT

This message (and any associated files) is intended only for the use
of the addressee and may contain information that is confidential,
subject to copyright or constitutes a trade secret. If you are not the
intended recipient, you are hereby notified that any dissemination,
copying or distribution of this message, or files associated with this
message, is strictly prohibited. If you have received this message in
error, please notify us immediately by replying to the message and
deleting it from your computer. Messages sent to and from us may be
monitored. Any views or opinions presented are solely those of the
author and do not necessarily represent those of the company. [v.1.1]

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Rich Jesse
Sent: Thursday, May 23, 2013 2:28 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: the joy of version numbers

Starting to get off-topic here, but regarding OFA, I unfortunately did not 
include a 4-digit version directory in the $OH path.  I will be doing that on 
new servers.  I also use a modified version of OFA where "/oradata" is not 
under $ORACLE_BASE.  I spend a fair amount of time in the command line at some 
level of the "/admin" directory, whether it be scripting, maintenance, or 
looking through logs.  I do not want to accidentally be anywhere near the data 
when I'm "rm"ing.  In a related note, I also don't care for the redo extension 
of ".log", which Cary has kindly explained here in the past.

So I use a modified OFA.  I hope I've been "Thinking Clearly" :) and changed 
what parts of those wonderful guidelines that I determined needing changing for 
my installations.  I think that's part of a DBA's duties.

And now that I understand the reasoning behind the "/unn" naming in OFA (Cary's 
explanation), I'll probably be stepping away from it.  For this install.  Maybe 
not for the next one...

"It depends"  :)

Rich

--
//www.freelists.org/webpage/oracle-l



--
//www.freelists.org/webpage/oracle-l


Other related posts: