Sorry, that doesn't make it for me. ASM is part of the kernel. If we plac=
ed every part of the kernel in a separate home just in case patches affecte=
d other parts of the kernel, we'd have to have a LOT of ORACLE_HOME's! :) =

=

If an ASM patch causes problems with other parts of the kernel, it's a bug =
and should be logged as such. The overhead I mentioned before doesn't seem=
(to me anyway) to warrant a separate install just in case that occurs. Ot=

>> ASM is part of the database kernel - if you want you can run the ASM>> instance and the DB instance using ASM from the same software home.
Still=3D
>> I'd think most would want to maintain separate software homes for ASM
and=3D
>> databases.

>Forgive my obtuseness (it is after all 2 am and I haven't had my first
coff=3D
>ee yet), but why would you want to do this? All I can see this causing is=

=3D
>additional overhead in terms of two sets of software to maintain, install
a=3D
>nd so on. I can't see a single benefit to this.

Say you have to apply a patch to fix an ASM specific problem. Having a
separate OH for the ASM instance you wouldn't have to test/worry about what=

impact the ASM patch would have on your database. =

Sten

Please see the official ORACLE-L FAQ: http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.