My Oracle Support Banner

DATAGUARD MIGRATING A PRIMARY AND STANDBY SITE TO NEW STORAGE WHEN ASM IS IN USE (Doc ID 829516.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Generic (Platform Independent)

Goal

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure: 

Device Names: /dev/sdf,/dev/sdg,/dev/sdg1,/dev/lizardr5/
Directory Name: /dev/oracleasm/ and it's sub-directories
Diskgroup Names: DATA01,DATA02,FRA01,FRA02,BACK01
Database Names: stdby10
Databases:
stdby10_gal - Primary database
stdby10_inv - Physical standby database
stdbylog_inv - Logical standby database

************

To add a new SAN to the primary and standby sites, present this new storage to ASM at each site and replace the storage currently allocated to the ASM disk groups with the new storage.

There is to be no impact the primary and standby sites while this is performed once the new storage is made available to the primary and standby nodes.

Assumptions:

1. The new storage can be presented to the primary and standby nodes at the same time the old storage is in place, that is both new and old can co-exist.
2. The diskgroup names in place at the primary and standby sites are going to remain the same.
3. There is no requirement to have the old storage remain in place in the environment and a second copy of the primary and standby database kept on this storage. 


Overview of tasks  performed:

This scenario is going to rely on ASM to perform the tasks required to add the new storage to an existing diskgroup and drop the old storage. There will be no downtime or impact on the primary and standby sites in any shape or form other than the additional IO that will be performed while the ASM rebalance shifts data from the old storage to the new storage during the alter diskgroup command.

The configuration is as follows:

64 bit Linux, Oracle 11.1.0.7 ASM, Oracle 10.2.0.4 Primary and Standby
ASM, Oracle Managed Files, 2 existing diskgroups DATA01, FRA01
Openfiler
ISCSI
1 Primary
2 Standby, 1 physical and 1 logical

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.