Re: Multiple ASM instances on the same box
Date: Fri, 20 Nov 2009 02:46:55 -0800
I agree with this.
With the setup we had from prior history, I created the 220.127.116.11 ASM Home; sourced the 10.2.0.4 ASM Home; brought down the ASM instance under the 10g home and tried to bring up the ASM instance under 18.104.22.168 ASM Home. This does not work becaue there are other 10.2.0.4 ASM instances (belonging to other databases). So the objective was to upgrade one database to 22.214.171.124 (having its own ASM instance). In prod this is not an issue because we dont have that setup there. It is only the dev environmetns where we have this setup.
On Fri, Nov 20, 2009 at 2:35 AM, Martin Berger <martin.a.berger_at_gmail.com>wrote:
> I did some _tests_ with such a setup, it works fine but is very
> confusing for everyone.
> One point to mention: an instance can only access _one_ ASM-instance
> at a time. (the 'first' used DG defines the ASM-instance)
> I never ever tried to run this setup in a prod env.
> On Fri, Nov 20, 2009 at 11:05, Kumar Madduri <ksmadduri_at_gmail.com> wrote:
> > Hence my question on if there were any clients that did setup this way
> > any reason (good or bad).