DATAGUARD MIGRATING A PRIMARY AND STANDBY SITE TO NEW STORAGE WHEN ASM IS IN USE
Last updated on OCTOBER 18, 2016
Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 184.108.40.206 - Release: 10.2 to 11.1
Information in this document applies to any platform.
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.
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:
ASM, Oracle Managed Files, 2 existing diskgroups DATA01, FRA01
2 Standby, 1 physical and 1 logical
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms