Re: a quick poll regarding the 11gR2 OFA

  • From: japplewhite@xxxxxxxxxxxxx
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Tue, 11 May 2010 10:05:30 -0500

We used to use the old OFA with /u001 - /u016 when our servers had 
dedicated disks, but now that we're on really good SAN with excellent UNIX 
Sys Admins that work well with us to "slice and dice" it, we do something 
similar to what Rich does.  Our database servers are dedicated to Oracle 
databases, so our layout doesn't have to accommodate other software.

Everything is under /oracle - all database files are under oradata1/SIDx/, 
two sets of Oracle-mirrored RedoLogs and ArcLogs are under oradata1&2, and 
oradata3 only has the 3rd of 3 Oracle-mirrored Control Files.  Easy and 
logical to navigate, nothing is too deep in a hierarchy, and SAN 
performance is great.  Also, makes it trivially easy to move the contents 
of an entire /oracle filesystem to a new server, which we've done several 

Works very well for us.  Doubt if we'll change when we go to 11g.


Jack C. Applewhite - Database Administrator
Austin I.S.D. - MIS Department
512.414.9250 (wk)  /  512.935.5929 (pager)

From:   "Rich Jesse" <rjoralist@xxxxxxxxxxxxxxxxxxxxx>
To:     oracle-l@xxxxxxxxxxxxx
Date:   05/11/2010 09:16 AM
Subject:        Re: a quick poll regarding the 11gR2 OFA
Sent by:        oracle-l-bounce@xxxxxxxxxxxxx

> A quick poll.
> The 11gR2 linux OFA version seems to push to use a directory such as
> “/u01/…” instead of “/opt/oracle/”
> Which directory are you currently using?

You asked for it!  :)

We currently use the "/unn" mount points, which unfortunately was already 
place before I came here.

Frankly, I don't care for the practice.  Perhaps it's from cutting my 
on VMS 4.3, but I prefer how VMS encourages admins to use "logicals" as a
layer of abstraction to give meaning and uniformity to generic disk/device
names and directory structures across many systems.

Enter Unix/Linux.  How many "/unn" shops have "/u03/oracle/arch/sid/"
directory structures under the "/u03" MP?  Likewise with
"/u02/oracle/data/sid/", "/u05/oracle/redo1/sid/" -- why even have the
"/unn" then?  It's unnecessary and confusing.  And the combination of 
two can be dangerous.  What is "/u01" on a non-Oracle box?  How much more
difficult is for a Jr/New DBA/SA to learn and know the directory structure
of each system?

I'm currently thinking through my own OFAesque structure.  I think OFA is
great, with just a few exceptions (most notably using ".log" for redo file
extensions, but I digress).  While I've been a fan in the past of 
the software in /usr or /opt (depending on OS flavor), that seems to have
fallen out of style for some reason.  My current incarnation is something
like this:


The structure should be obvious, with each "/oraxxx" being it's own mount
point.  I specifically did not break out redos as I've not been able to
prove any performance reasons for doing so (i.e. using different options 
the mount point for our SAN), although I probably will for clarity, which 
always a good thing during emergencies like a recovery.

The other structure I'm considering is more traditional, with the
aforementioned /opt housing $ORACLE_HOME:


The only problem with this structure for me is that I often have to play
around in the FRA directory (much to my chagrin), so I'm leaning more
towards the former.

Also, I've not considered the DIAG area yet, as we're still on 10g.  I'll 
course incorporate that for our move to 11g.  It's a Work In Progress™ 

My $.02,

> Are you going to change your directory structure to match this new OFA
> structure?


Other related posts: