Veritas Storage Foundation 5.0 for Oracle RAC Configuration Guide Extracts for HP Serviceguard Storage Management Suite, Second Edition, May 2008

Using Storage Checkpoints and Storage Rollback

Using the Storage Checkpoint Command Line Interface (CLI)

Chapter 4

Using the Storage Checkpoint Command Line Interface

(CLI)

Veritas Storage Foundation for Oracle RAC provides a command line interface to many

key operations. The command line interface lets you incorporate command operations

into scripts and other administrative processes.

NOTE The SG Oracle RAC command line interface depends on certain tablespace and container

information that is collected and stored in a repository. Some CLI commands update the

repository by default. It is also important to regularly ensure the repository is up-to-date

by using the dbed_update command.

NOTE For SG Oracle RAC database, when you issue the commands, replace $ORACLE_SID with

$ORACLE_SID=instance_name and provide the instance name on which the instance is

running.

Overview of Commands

SG Oracle RAC commands supported in the command line interface are located in the

/opt/VRTS/bin directory. Online manual pages for these commands are located in the

/opt/VRTS/man directory.

Table 4-3 summarizes the commands available to you from the command line.

Table 4-3 Veritas Storage Foundation for Oracle RAC Commands

Command Description

dbed_update Creates or updates the repository in Veritas Storage

Foundation for Oracle RAC

dbed_ckptcreate Creates a Storage Checkpoint for an Oracle database

dbed_ckptdisplay Displays Storage Checkpoints associated with an Oracle

instance

dbed_ckptmount Mounts a Storage Checkpoint for an Oracle instance

dbed_ckptumount Unmounts a Storage Checkpoint for an Oracle instance

dbed_ckptrollback Rolls back an Oracle instance to a Storage Checkpoint

point-in-time image

dbed_ckptremove Removes a Storage Checkpoint for an Oracle instance

dbed_clonedb Creates a copy of an Oracle database by cloning all existing

database files and recreating the control file accordingly. This

cloned database can only be started on the same host as the

existing database as long as it uses a different SID.