Re: ASM RAC Database from one RAC to another

From: Sanjay Mishra <>
Date: Sat, 16 May 2009 07:44:54 -0700 (PDT)
Message-ID: <>


THought to share with everybody as what I assume earlier is correct and we can go from one cluster to another cluster with only small downtime. I am able to see the Diskgroup on both nodes. Ofcourse it is not mounted on Second RAC. I created few tem tables in First RAC, Then I stopped the Database on 1RAC and started on 2nd RAC and checked the Tables and then drop these tables and stop the Database on Second RAC. Then I started the Database on 1st RAC. So I can be able to move without any issue.

I did it earlier with non-RAC and was not sure if there is any issue with RAC enviroenment with the exception that you have to make sure that it is added in the OCR

Thank to all for all comments


From: Martin Berger <>
Sent: Saturday, May 16, 2009 1:08:53 AM
Subject: Re: ASM RAC Database from one RAC to another


this will destroy the "sanjay" DG.
I'm pretty sure Sanjay wants to migrate the DB from one ASM to another without deestroying it?
In this case I'd suggest
1)shutdown "sanjay" db on 1st RAC
2) make all LUNS unavailable on 1st RAC (this might need a reboot of the ASM-instance - depending on version and some configurations)
3) make ALL LUNs available on 2nd RAC
4) rescan for new ASM-DISKs in 2nd RAC
5) mount the DB in 2nd RAC
6) srvctl add & start "sanjay" on 2nd RAC

make sure there is no time, where tha ASMs of both RACs can see the same Disks simultaniously.

there are a lot of possible pitfalls in such a migration, depending on the ASM-config, OS, underlying Hardware, Versions, so test, test, test


> Sanjay,
> At the very least, the headers for the LUNs utilized by the "sanjay"
> database need to
> be cleared up (either via drop diskgroup OR dd OR as a last resort -
> force option in
> the create diskgroup while adding to the 2nd RAC environment) -
> basically anything
> which clears up the header status of those LUNs/Diskgroups.
> Once those diskgroups have been cleared up from the metadata of the "sanjay"
> database, it should be relatively less challenging.
> -Rajeev
> On Fri, May 15, 2009 at 1:59 PM, Sanjay Mishra <> wrote:
>> Hi
>> I want to have some insight from somebody who has done the following or has
>> face such situation.
> 3. Make the LUNS used by ASM for sanjay  database on Second RAC environment.
>> Any suggestion or issues in the above setup
>> Thanks
>> Sanjay
> --

Received on Sat May 16 2009 - 09:44:54 CDT

Original text of this message