HP 3PAR Application Software Suite for Oracle - Manual (Page 8)

The following example displays the location of the Recovery Manager for Oracle repository on
the backup server for Oracle database instance test that is running on database server Host1.
/etc/3par/solutions/Host1.ora.test
If the database is a Real Application Cluster (RAC) database, there will be multiple repositories,
one for each RAC instance.
Interacting with Oracle
HP 3PAR Recovery Manager for Oracle interacts with Oracle database through the SQL Plus utility
to perform the following:
•
Retrieve database structure information in order to create virtual copy for the database.
•
Interact with the Oracle database (putting database in backup mode, stopping redo applied
process or performing database log switching) as necessary to create a consistent virtual copy.
In order to create a consistent virtual copy of an Oracle database, the database structure must
satisfy the following requirements:
•
The database must be running in archive log mode and automatic archiving must be enabled
in order to create an online virtual copy, datafile virtual copy, or archive log virtual copy.
•
Datafiles and archive logs must reside on separate 3PAR virtual volumes.
•
The online redo logs and control files should not reside on the virtual volumes used by the
datafiles and archive logs to avoid being rolled back along with datafiles and archive logs
virtual volumes. However, the online redo logs and control files can share the same 3PAR
virtual volumes.
•
If the database files reside on Symantec VxVM volumes, datafiles and archive logs must reside
on separate VxVM disk groups. The online redo logs and control files should reside on separate
VxVM volumes used by the datafiles and archive logs.
•
If the Oracle database is an ASM managed database, the datafiles and archive logs must
reside on separate ASM disk groups. The online redo logs and control files should not reside
on the same ASM disk groups used by the datafiles and archive logs to avoid being rolled
back when using the Recovery Manager Rollback feature.
•
ASM disk groups should not be shared between different databases.
•
If you use HP LVM Volume Manager, the Oracle datafiles and archive logs must reside on
separate LVM volume groups. In addition, online redo logs and control files must not reside
on LVM volume groups that are used by Oracle datafiles and archive logs. However, the
online redo logs and control files can reside on the same LVM volume group.
•
If the database is an RAC database, all RAC instances must share the same archive log
destinations (same cluster file systems or same ASM disk groups).
To ensure that the database is running in automatic archive log mode, use SQL Plus to ensure that
the Database log mode is Archive Mode and that Automatic archival is Enabled, as
in the following example:
$ sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.1.0 - Production on Wed Nov 14 13:59:13 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> archive log list
8 Overview of Recovery Manager Operations