In comp.unix.solaris Richard B. Gilbert <rgilbert88@comcast.net> wrote:
> Colin B. wrote:
>> In comp.unix.solaris ehabaziz2001@gmail.com wrote:
>>
>>>Let say for Oracle application ?
>>
>>
>> And what is your hardware?
>>
>> When you say "Oracle Application," do you mean a database-backed application,
>> or Oracle itself (which would make this a database box)?
>>
>> There's no way I would put a database on an OS disk in anything other than
>> a playground for myself. Also, Oracle makes some very strict demands on what
>> is required for swap space, so my thought would be:
>>
>> / s0 20GB
>> <swap> s1 Whatever Oracle recommends
>> overlap s2 (whole disk)
>> /var s3 10GB
>> metadb s7 >24MB (massive overkill)
>>
>> ...and if home directories are going to be on the local disk,
>> /export/home s4 (remaining disk less 20GB)
>>
>> Then put Oracle on an external disk.
>>
>
> Shouldn't the Oracle executables be put in /opt?

Depends on the particulars of the site. Our Oracle binaries are in their
own directory, but on local disk at any rate.

> The database itself should normally be spread over five or more
> spindles. Don't put both a table and its indices on the same drive and
> put redo logs on a disk by themselves.
>
> Oracle makes some very specific recommendations for allocating disk
> space. If you need to ask, find those recommendations and obey them as
> if they were holy writ! You can break the rules if the data base is
> small, simple, and performance is not terribly important but, if that is
> the case, why are you using Oracle?

Agreed. There are certain situations where breaking the rules makes clear
sense, but you REALLY need to know what you're doing, if you don't want to
mess things up.