oracle binaries - keep with server or with package?

[Daryl Much]

I'm wondering where is the recommended location for the oracle binaries ($ORACLE_HOME) on an MC/SG active/active cluster? Should it be kept on a logical volume associatied with the oracle package or should it be kept in local non-shared storage. I can see advantages (and disadvantages) to each setup.

In our case we have exactly 2 oracle packages running on 2 nodes. At this time each node keeps the oracle binaries (and ORACLE_BASE also) on vg00. I am considering moving them to a shared-exclusive LV. This way patches, logfiles, config files, etc will always follow the specific instance.

Thanks for any perspective on this...

Chuck Davis

[Rajeev Tyagi]

Chuck,

It is better to have oracle binaries on local disk instead of shared disk as it will reduce your downtime during oracle maintenance.

[A. Clay Stephenson]

I prefer to move the Oracle binaries with the package. You should have enough room to install at least two versions of the binaries so that the install step can be done with the package up. The actual database upgrade will then have to be done during a maintenance window. I also dedicate a single-purpose listener to each package.

If you are going to do this, you must keep the nodes at the same patch level so that shared libraries don't cause an Oracle problem.

[Travis Harp_1]

I would think that in an active/active cluster your best bet would be the binaries moving with the package.
If you were in an active/standby situation then there could be a case for having them local to do upgrades on one, fail over and upgrade the other but with the binaries active on each system your not going to get that advantage anyway.

Also, having Oracle point to a link such as "production", allows you to install upgrades, bring down the database and switch the link.
It will save you some time during an upgrade window.

[Steven E. Protter]

You can do it either way.

Keeping them with the package saves space. You only need one copy of them for both nodes. If oracle is not running on the node, why does it need to be there taking up all that space.

But you do what you are most comfortable with.

SEP

[Jeff Schussele]

Hi Chuck,

For us it has at times boiled down to licensing $.
If you have two servers with 4 CPUs each and a set of binaries on each you have to pay an eight CPU license. IF you float the binaries with the package you only have to pay a 4 CPU license.
But we do it both ways here & each way has its merits.

My 2 cents,
Jeff

[Daryl Much]

Thanks everyone. Those were exactly the answers I was looking for.

Regards,

Chuck Davis

[TwoProc]

My preference is to move the binaries with the package - even though there are many reasons why others would disagree and they all have good points. However, I want my binaries to move b/c it means that I'm assured that the production data moves with the production patched-binaries *every* time. Not just when we remember to keep them patched. I feel better knowing that SG is bringing up exactly what it had on the production box. Also, be aware that the service guard scripts that you get from HP don't plan on working this way - they REALLY want you to have the ORACLE binaries on local disk on each machine. It took a bit of extra manipulation to make it work that way, and HP consulting gave me the official "our official Oracle MC/SG scripts are not supported for that configuration..." yada, yada, yada. I had them do it with moving the binaries anyway.