File Syetem Lay Out - Question .

[blal]

Dear All ,

Need suggetions from you .

This is how we build DB file systems on our Database Servers .These standards are set by our previous sysadmin .

I have few questions in my mind .

/opt/local/xxyyzzz is a file system (100MB)
And all other file system are mounted on this mounted file system.(All are vxfs file systems)

lly oradata is a directory on /opt/local/xxyyzzz file system and Couple of other file systems are getting mounted on to it .

Is this a recommended architecture ? what are the short comings of this lay out ? is there any performance related issues be seen here ?


Your advice will be deeply appreciated .


/opt/local/xxyyzzz
/opt/local/xxyyzzz/backup
/opt/local/xxyyzzz/control001
/opt/local/xxyyzzz/home
/opt/local/xxyyzzz/admin
/opt/local/xxyyzzz/control003
/opt/local/xxyyzzz/control002
/opt/local/xxyyzzz/oradata/arch002
/opt/local/xxyyzzz/oradata/redo001
/opt/local/xxyyzzz/oradata/data006
/opt/local/xxyyzzz/oradata/data002
/opt/local/xxyyzzz/oradata/undo001
/opt/local/xxyyzzz/oradata/data004
~

[A. Clay Stephenson]

One of the things that really jumps out at me is that you are using /opt for a purpose that is not intended. /opt is really to be used for executables rather than data. It would be fine to store your Oracle executape under something like /opt/oracle/app/product/9.2.x but the data should really be in some unrelated located.

It is not clear that you are listing filesystems or simply directories but in general for oracle, at least, several filesystems are a good idea. However, there are times when only one filesystem will suffice for data, indices, redologs, and archives --- but still the executables should be somewhere else. If your data are housed in conventional individual disks (e.g. JBODS) then the more you can scatter your data across multiple filesystems the better but if you are using a modern cache-centric array with high-bandwidth connections then you may find that lumping everything into one filesystem performs almost as well --- and maintenance and backups become easier.

[spex]

Hello,

Typically, Oracle filesystems have their mountpoints at root ("/"). For example:

/backup/yoursid
/oraarch/yoursid
/u01/oradata/yoursid/datafile.dbf
/u01/oradata/yoursid/control001.ctl
/u02/oradata/yoursid/undo01.dbf
/u02/oradata/yoursid/control002.ctl
...

The previous sysadmin was probably (incorrectly) following the UNIX convention that locally-installed, optional software resides in /opt/local. However, if this server's "raison dâ être" is to serve as a database server, Oracle datafiles, control files, etc. really aren't optional. What's more, /opt is only intended to contain binaries, not variable data.

Make life easy on yourself and create new mountpoints off of root. Of course, you'll have to perform any house-cleaning (changing absolute paths in scripts, init.ora, Oracle's data dictionary, etc.) associated with the transition.

PCS

[Geoff Wild]

Our DBA's just moved to a new standard.

/v00 oracle binaries and scripts (50GB)
/v01
/v02
/v03
.
.
and so on are 500GB file systems for data, indexes, redo files.

The nice thing about that - I know longer have to manage their space - they do. They can move the data arounf the v0* filesystems as they see fit.


Except in SAP where it is:

/oracle/
/oracle//arch
/oracle//sapdata01
/oracle//sapdata02
/oracle//sapdata03
.
.
and so on...where is the SAP Instance name.

Rgds...Geoff

[Dennis Handly]

Another thing to add to what Clay and PCS mentioned is that /opt/ is intended to be read only. And in /var/foo/ is where the writeable files are suppose to be.