I should have stated that differently. Yes, I hope we can all agree
that a different MP for the database is usually a good thing. But what
I had meant was our database mount point is not in the $ORACLE_BASE
tree. e.g.:
MYDB;/opt/oracle> df -k
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/opt 5039406 157625 4831387 4% /opt
/dev/vx/dsk/orabin_vol/ora_binaries
6291456 3358952 2909656 54% /opt/oracle
/dev/vx/dsk/oradb_vol/mydb_vol
12582912 6112920 6419456 49% /oracle/mydb
/dev/vx/dsk/oradb_vol/redo2_vol
512000 154828 351600 31%
/oracle/mydb/redologs2
/dev/vx/dsk/orabin_vol/control1_vol
1048576 6672 1033776 1%
/oracle/mydb/control1
/dev/vx/dsk/orabin_vol/archive_vol
5242880 67536 5134984 2%
/oracle/mydb/archive
/dev/vx/dsk/oradb_vol/redo1_vol
512000 154820 351608 31%
/oracle/mydb/redologs1
/dev/vx/dsk/orabin_vol/control2_vol
1048576 6672 1033776 1%
/oracle/mydb/control2
Other than that, OFA all the way, baby! :)
Rich
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of David Sharples
Sent: Thursday, October 06, 2005 12:00 PM
To: Rodd.Holman@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: 10.2 locations for Admin and Oradata directories
reading the ofa paper now, nowhere can I see it say put the data on the
same mount point as the software
[quote]
Intuition tells most installers that Oracle database files should be
separated from other files on a system. There are concrete reasons for
doing so, among which: database files' lifespans differ from all other
files on your system; and database files will require a different backup
strategy than the other files on your system. A thoughtful naming
strategy for database files eliminates a whole class of administrative
problems.
[/quote]
On 10/6/05, Rodd Holman <Rodd.Holman@xxxxxxxxx> wrote:
Our datafile location (/oradata) is never
mounted under $ORACLE_BASE. Keeps them nice and tidy in their own
little/large playground.
--
http://www.freelists.org/webpage/oracle-l