In article <1174072591.791254.110620@d57g2000hsg.googlegroups .com>,
learner <Zabaloch@gmail.com> wrote:
>Hey Richard,
>I am just worried about the binaries for the Orale DB at the moment. I
>know it requires a lot of disk, but all of that will be created over
>the SAN. I am not sure about all of that part, but I am hoping the DBA
>would do that part.

Silly question: other than that the Oracle binaries take up smaller
amount of space than your SAN prople probaly want to allocate a LUN
for, why don't you just carve off a LUN from the SAN for the Oracle
binaries?

In general, you'll only need one partition for each unique set of
Oracle binaries (e.g., one for /oracle/product/9.2, one for
/oracle/product/1.2, etc.). Each of these will be relatively small.

You *might* also want to create an area for $ORACLE_HOME so that
your dba doesn't fill your harddrive while staging install files.

>I am currently writing up the process that I would have to follow in
>order to install just the Oracle Binaries on a particular server.

Like I said, parent directory for the Oracle binaries. This can
be a subdirctory of any filesystem on your root drive, its own
slice off the root drive, a dedicated SAN-local LUN. How you do
it depends greatly on your environment's policy or your/your dba's
preference. The binaries are the *easy* part (you want real fun,
wait till they want to deploy a multiple-SID RAC 10g environment!)

-tom


--

"You can only be -so- accurate with a claw-hammer." --me