Recovery Manager for Oracle User’s Guide

2.3 Interacting with Oracle

3PAR Recovery Manager 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 (put tablespaces (or the whole database) in and out of backup mode, switch logfiles) 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 only virtual copy, or archive log only 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 Veritas 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 restored when using the Recovery Manager Rollback feature.

ASM disk groups should not be shared between different databases.

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).

2.4

Interacting with Oracle

Page 20
Image 20
HP StoreServ Application Suite for Oracle Media manual Interacting with Oracle