Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

SFORA dbed_vmchecksnap ERROR V-81-5677 Could not find a mandatory,
primary and valid archive destination for database PROD.
Please review the LOG_ARCHIVE_DEST_n parameters and check v$archive_dest.
This example shows how to establish a mandatory archive destination using
SQL*Plus:
alter system set log_archive_dest_1 = \
'LOCATION=/ora_mnt/oracle/oradata/PROD/archivelogs MANDATORY \
[REOPEN]' [scope=both];
For more information about Oracle parameters for archiving redo logs, see your
Oracle documentation.
Validating a snapplan (dbed_vmchecksnap)
After creating a snapplan, the next steps are to validate the snapplan parameters
and check whether the snapshot volumes have been configured correctly for
creating snapshots. If validation is successful, the snapplan is copied to the
repository. The snapplan is validated using the dbed_vmchecksnap command with
the -o validate option.
In Veritas Storage Foundation for Oracle RAC configurations, dbed_vmchecksnap
with the -o validate option can be executed on the VxVM CVM master or slave
node.
Consider the following prerequisites and notes before validating a snapplan:
■ The database must be up and running while executing the
dbed_vmchecksnap command.
Prerequisites
■ The dbed_vmchecksnap command must be run as the Oracle
database administrator.
■ The default behavior is to force validation. Use the -n option if
you want to skip validation.
■ After validating the snapplan, you have the option of modifying
the snapplan file to meet your storage configuration requirements.
■ If a snapplan is updated or modified, you must re-validate it. It is
recommended that snapplans are revalidated when changes are
made in the database disk group.
■ The dbed_vmchecksnap command can be used on the primary
or secondary host. RAC-specific
■ See the dbed_vmchecksnap(1M) manual page for more
information.
Usage notes
263Using Database FlashSnap for backup and off-host processing
Validating a snapplan (dbed_vmchecksnap)