HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

4. Recover the RAC database ASM11GR2.
Assume the Oracle binary is available and CRS is up. Mount all necessary file systems if the
file systems are used. In this case, asmlib is used, so scan the oracleasm disks and then mount
all database diskgroups.
a. Scan oracleasm devices.
dl160g6-13:# oracleasm scandisks
b. Mount ASM diskgroups.
alter diskgroup ASM11GR2_ARCHDG mount;
alter diskgroup ASM11GR2_ARCHDG2 mount;
alter diskgroup ASM11GR2_DATADG mount;
alter diskgroup ASM11GR2_DATADG2 mount;
alter diskgroup ASM11GR2_REDODG mount;
c. Start the ASM11GR2 database.
[vcdba@dl160g6-13 ~]$ sqlplus '/as sysdba'
SQL*Plus: Release 11.2.0.1.0 Production on Wed Jun 8 18:11:30 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 835104768 bytes
Fixed Size 2217952 bytes
Variable Size 641730592 bytes
Database Buffers 184549376 bytes
Redo Buffers 6606848 bytes
Database mounted.
Database opened.
d. Repeat this operation to bring up other RAC nodes.
Recovering to the Asynchronous Periodic Backup System when the Local
and Synchronous Backup Systems are Unavailable
In this scenario, the local system S256 and synchronous backup system S347 are both unavailable.
The primary database ASM11GR2 cannot be brought up using the local system S256 and cannot
be failed over to the synchronous backup system S347.
146 Case Study: Remote Copy with Recovery Manager for Oracle