RE: Oracle Home naming convention

From: Patterson, Joel <Joel.Patterson_at_crowley.com>
Date: Mon, 26 Nov 2012 12:41:22 -0500
Message-ID: <C95D75DD2E01DD4D81124D104D317ACA1C764F21F0_at_JAXMSG01.crowley.com>



Thanks,
I ran into an issue with cloning the Oracle Homes a while back so I don't anymore. I have looked around for some notes on it, but have not found it yet. I believe it was an SR and that SR has since cycled out.

The PSU's are quick and easy, and I'm just getting started with this, still have issues getting all the 'business' units/databases sharing the same oracle home to agree together on the downtime regardless of how long. Rolling back is supposed to be easier, and I suppose it is by taking a 'snapshot' (solaris) of the database, and just restarting it in the old home.

Joel Patterson
Database Administrator
904 727-2546
From: Wayne T Smith [mailto:wts_at_maine.edu] Sent: Monday, November 26, 2012 10:32 AM To: Patterson, Joel; ORACLE-L
Subject: Re: Oracle Home naming convention

  • I'd clone the latest home rather than install again.
  • I don't have separate homes for PSUs, because applying a PSU is so easy and quick compared to an install or even a clone.

Cheers, Wayne
Patterson, Joel wrote, in part, on 11/26/2012 10:17 AM:

-----Original Message-----

From: Patterson, Joel

Sent: Monday, November 26, 2012 10:17 AM

To: 'oracle_at_dunbar-it.co.uk<mailto:oracle_at_dunbar-it.co.uk>'; oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>

Subject: RE: Transportable Tablespaces and Deferred segment creation "bug"

Ahem :),

Speaking of oracle homes, I am still experimenting with naming conventions and the out-of-line patching. So looking for input.

I decided lately to spell out the oracle version, (and I had no reason for numbering dbhome_1, _2).

Like.

/orasoft/app/oracle/product/11.2.0.3.0/dbhome

/orasoft/app/oracle/product/11.2.0.3.3/dbhome

etc..

The original reason was to upgrade and patch databases one at a time, say 11.2.0.1.0 to 11.2.0.3.0, and 11.2.0.3.0 to 11.2.0.3.3. One result is upgrading through a version, say to 112033 leaves an empty oracle homes like 10g, 112010, or 112030, which can be cleaned up, or left in place for later upgrading of other databases.

Now, if I get another PSU, I think I have to install the base 112030 in a new home say, 11.2.0.3.5, and apply the PSU 112035?

So the jury is still out on whether or not this is an optimal idea or not. Any comments from the list? Any other naming conventions that the listers like over others?

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Nov 26 2012 - 18:41:22 CET

Original text of this message