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.
Consider the following prerequisites and notes before validating a snapplan:
dbed_vmchecksnap
command:
$ /opt/VRTS/bin/dbed_vmchecksnap -S
ORACLE_SID
\
-H
ORACLE_HOME
-f
SNAPPLAN
-o validate
Note In HA environment, you must modify the default snapplan, use the virtual host name defined for the resource group for the PRIMARY_HOST and/or SECONDARY_HOST, and run validation.
In the following example, a snapplan, snap1
, is validated for a snapshot image in a same-node configuration. The primary host is host1
and the working directory is /export/snap_dir
.
$ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -H /oracle/product/10g
\
The version of PRIMARY_DG-PRODdg is 110.
The database is running in archivelog mode.
ARCHIVELOG_DEST=/prod_ar is mount on /dev/vx/dsk/PRODdg/prod_ar.
Examining Oracle volume and disk layout for snapshot
Volume prod_db on PRODdg is ready for snapshot.
Original plex and DCO log for prod_db is on PRODdg01.
Snapshot plex and DCO log for prod_db is on PRODdg02.
SNAP_PRODdg for snapshot will include: PRODdg02
The snapplan snap1 has been created.