Home > Veritas Storage Foundation™ for Oracle Manual Pages

DBED_CKPTROLLBACK (1)

User Commands

Table of contents


NAME

dbed_ckptrollback - roll back an Oracle database, tablespace, or datafiles to a Storage Checkpoint

SYNOPSIS

dbed_ckptrollback -S ORACLE_SID -H ORACLE_HOME -c CKPT_NAME

     [ -T TABLESPACE | -F DATAFILES | -f DATAFILE_LIST ]
     [ -b BUFF_SIZE ] [ -t THREADS ]
     [ -i ] [ -h ]


AVAILABILITY

Veritas Storage Foundation for Oracle. To determine whether this product is installed on an \1 system, enter:

lslpp -L VRTSdbed


DESCRIPTION

The dbed_ckptrollback command rolls back an Oracle database, tablespace, or datafiles to a specified Storage Checkpoint. You cannot roll back tablespaces or datafiles to an instant Storage Checkpoint. For information about instant Storage Checkpoints, see dbed_ckptcreate(1M).

Database rollback requires that the database be shut down before Storage Rollback begins. The dbed_ckptrollback command will not begin if the Oracle database is up.

After Storage Rollback is complete, the Oracle database must be recovered using Oracle recovery.


OPTIONS

The following options are supported:
-S ORACLE_SID
Specifies the name of the Oracle database that will be rolled back.
-H ORACLE_HOME
Specifies the ORACLE_HOME setting for the current Oracle database.
-c CKPT_NAME
Specifies the name of the Storage Checkpoint to roll back to.
-T TABLESPACE
Specifies the name of tablespace to be rolled back. You cannot roll back tablespaces to an instant Storage Checkpoint.
-F DATAFILES
Specifies the names of datafiles to be rolled back. You cannot roll back datafiles to an instant Storage Checkpoint.
-f DATAFILE_LIST
Specifies the list of datafiles to be rolled back. You cannot roll back a list of datafiles to an instant Storage Checkpoint.
-b BUFF_SIZE
Specifies the buffer size to be used for Storage Rollback. The buffer size may be between 1,024 bytes and 10,240,000 bytes, and must be a multiple of 512. Tuning the Storage Rollback buffer size can greatly affect performance. The default value is 128k (131,072 bytes).
-t THREADS
Specifies the number of threads to be used for Storage Rollback. The number of threads specified may be between 1 and 64. Any files to be rolled back will have the specified number of threads applied to the task. Tuning the Storage Rollback thread pool can greatly affect performance. The default value is 8 threads.
-i
Sets interactive mode.
-h
Shows command usage.

NOTES

dbed_ckptrollback must be run as the Oracle DBA user. The superuser cannot run Storage Rollback, since there is no guarantee that the database status can be determined correctly.

Only database rollback is allowed for instant Storage Checkpoints. All the datafiles along with control files and online redo log files are rolled back. It is not possible to roll back tablespaces and datafiles to an instant Storage Checkpoint. After database rollback is complete, you must recover the Oracle database instance. Rolling the database forward is not supported; that is, you cannot apply archived redo logs.

The above commands run without interaction from the user. However, if you want to be prompted before critical actions are taken, use the -i option. If you are using this command for the first time, it is recommended that you use the -i option.

Database changes that have occurred since a Storage Checkpoint was created may make it impossible to run Storage Rollback successfully. Running Storage Rollback may be impossible if the control files for the database have recorded the addition or removal of datafiles. In order to provide recovery options for the database administrator, a backup copy of the control file for the database is saved in the SFDB repository just after a Storage Checkpoint is created. This file may be used by the database administrator to assist with database recovery if necessary. If possible, both an ASCII and a binary version of the control file will be left in the SFDB repository. The binary version will be compressed to conserve space. Recovery using alternate control files should be approached with care by experienced database administrators.


EXAMPLES

To roll back an offline Oracle database to a Storage Checkpoint:

$ /opt/VRTS/bin/dbed_ckptrollback -S PROD -H /oracle/product/9i \.br
-c Checkpoint_903937870

To roll back a tablespace of an offline Oracle database to a Storage Checkpoint:


$ /opt/VRTS/bin/dbed_ckptrollback -S PROD -H /oracle/product/9i \.br
-T DATA01 -c Checkpoint_903937870

To roll back datafiles of an offline Oracle database to a Storage Checkpoint:


$ /opt/VRTS/bin/dbed_ckptrollback -S PROD -H /oracle/product/9i \.br
-F /oradata1/data01.dbf,/oradata2/index01.dbf \.br
-c Checkpoint_903937870


SEE ALSO

dbed_ckptcreate(1M), dbed_ckptdisplay(1M), dbed_ckptmount(1M), dbed_ckptplan(1M), dbed_ckptpolicy(1M), dbed_ckptquota(1M), dbed_ckptremove(1M), dbed_ckptumount(1M), dbed_clonedb(1M), dbed_update(1M), oracle_edition(7)

Veritas Storage Foundation for Oracle Administrator's Guide Veritas Storage Foundation for Oracle RAC Installation and Configuration Guide ~

Last updated: 15 Jan 2006
Copyright ©2009 Symantec Corporation
All rights reserved.