Recovery Manager for Oracle User’s Guide

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

Archive Mode

Database log mode

Automatic archival

Enabled

Archive destination

/rac9i_db/rac9i_arch2

Oldest online log sequence

764

Next log sequence to archive

764

Current log sequence

765

2.4 Interacting with Veritas Volume Manager

Due to restrictions on VxVM, 3PAR Recovery Manager requires a minimum of two disk groups per database.

CAUTION: The archive log destination must reside on a different Veritas disk group than any of the disk groups that contain data files for backup operations. It is also recommended that all database data files be in one VxVM disk group.

Because of the Veritas VxVM disk group limitation of allowing only one imported VxDG per disk group, Recovery Manager allows only one virtual copy per database to be mounted at a time. You must unmount the virtual copy for a database after it has been backed up in order to mount another virtual copy.

Interacting with Veritas Volume Manager

2.5

Page 21
Image 21
HP StoreServ Application Suite for Oracle Media manual Interacting with Veritas Volume Manager