Re: Oracle Home naming convention

From: Wayne T Smith <>
Date: Mon, 26 Nov 2012 10:32:24 -0500
Message-ID: <>

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: '';
> 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/
> /orasoft/app/oracle/product/
> etc..
> The original reason was to upgrade and patch databases one at a time, say to, and to 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,, 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?

Received on Mon Nov 26 2012 - 16:32:24 CET

Original text of this message