Hi Clemens,
thank you for your answer.
I am a little worried about possible fragmentation.
I've had this problem a while ago (add a second disk to a diskgroup and
the drop the first disk). After the rebalance operation after drop
completed all full table scan operations were a couple of times slower
than before.
The way I solved the performance problem before as I had only one big
table was to create a new fresh tablespace and ALTER TABLE MOVE to the
new tablespace. Then the performance was restored to the previous state.
In this migration situation I am afraid this is not feasible thus I need
to consider other options.
The machine will be stopped anyway as controllers are to be
added/replaced.
Any thoughts on this?
Thank in advance,
Mihail Daskalov
-----Original Message-----
From: CLEMENS.BLEILE@(protected)]
Sent: Wednesday, October 11, 2006 1:58 PM
To: suse-oracle@(protected)
Subject: Re: [suse-oracle] SPAM: Which is the best way to migrate from
one storage array to another SAN?
Hi Michael,
option 2.) is the one to go. With this you can migrate without downtime.
You just have to wait until Oracle has rebalanced the data over the new
disks (i.e. no row in v$asm_operation anymore).
The OCR can be migrated using ocrconfig:
1. shutdown crs as root: crsctl stop crs
2. Use ocrconfig -showbackup to get the location and names of your
OCR-backup
3. change your /etc/oracle/ocr.loc and point to the new raw device or
alternatively change /etc/raw and point to the new device
4. Use ocrconfig -restore <file-name from 2.> to restore the OCR to the
new location
5. Run ocrcheck to check the OCR in the new location
6. start crs as root: crsctl start crs
The voting disk can be migrated using dd.
Ciao
Clemens
--- Original Message ---
> Hi, all
> I would like to ask for you opinion about how to migrate a 50
> GB Oracle
> 10.2.0.1 RAC database on SLES9 SP3/x84,
> which is currently on a storage with TWO luns , in which there
> are two
> partitions (one in each LUN) which are used trough ASMLib to
> form two
> ASM disks, which are used in turn to form two different ASM
> Diskgroups
> (DATA and FLASH_RA).
> I would like to change the storage array with minimal risk
> and
> relatively little downtime (up to 12 hours).
>
> What would be advisable method for this operation.
> I have thought about several ways for doing that:
> 1) (export database, create new ASM DISKS, create new DATABASE,
> import)
> 2) Create new ASM DISKS on the new LUNS from the new storage,
> add them
> to the current diskgroups, drop the former disks from the
> DISKGROUPs
> 3) Create new partitions, shutdown the database, clusterware,
> everything. Use dd if=/dev/sdOLD of=/dev/sdNEW; remove physically
> /dev/sdOLD and hope that ASMLib will recognize /dev/sdNEW in
> the same
> way (it will make the same ASMDisk appear).
> 4) Create new ASM DISKS on the new LUNS from the new storage;
> create new
> ASM DISKGROUPS from then; use RMAN to copy the datafiles, and
> control
> files; recreate redolog files
> 5) Create new ASM DISKGROUP for the database, then remove the
> old
> diskgroup and recover the database using FLASH RECOVERY AREA;
> then
> create new DISKGROUP for the FLASH_RA and change the
> recovery_file_dest
> to the new DISKGROUP
>
> How to change the OCR and Voting disks (I think there only dd
> option
> exists)?
>
> Thanks for your opinions and advices.
>
> Regards,
> Mihail Daskalov
>
> --
> To unsubscribe, email: suse-oracle-unsubscribe@(protected)
> For additional commands, email: suse-oracle-help@(protected)
> Please see http://www.suse.com/oracle/ before posting
>
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
