VERITAS Storage Foundation 4.1 Oracle Administrator's Guide

Chapter 12, Using the VERITAS Storage Foundation for Oracle Graphical User Interface
Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints
301
Rolling back a tablespace is used for complete recovery of the tablespace. It is not designed for
point-in-time (incomplete) tablespace recovery, which is more complicated and requires interaction
with Oracle Customer Support. The tablespace point-in-time recovery requires using a clone
database. See “Creating Clone Database” on page 282 for more information.
Note You can perform this operation while the database is online as long as the tablespace is
offline.
▼ To roll back a tablespace to a Storage Checkpoint
1. Verify that the tablespace to which you want to roll back is offline.
2. Click the a specific Storage Checkpoint in the object tree. (You may need to expand the tree
view to find the Storage Checkpoint.)
3. Select one of the following methods to rollback to the selected Storage Checkpoint.
◆ From the menu bar, select Storage Checkpoint > Rollback a Storage Checkpoint.
or
◆ Right click the Storage Checkpoint to which you want to rollback to bring up a pop-up
menu. Then, click Rollback a Storage Checkpoint.
If the database is online, you will receive a prompt asking you if you want to continue. Click
Yes to continue the Storage Rollback.
The Rollback a Storage Checkpoint wizard is displayed.
4. Verify that you are rolling back to the correct Storage Checkpoint and click Next to continue.
If you selected the wrong Storage Checkpoint, click Cancel. The information on this screen is
read-only.
5. On the second screen, use the drop-down menu to select the appropriate buffer size in the
Rollback Buffer Size field. The default buffer size is 128K.
Note The buffer size configured for reads and writes when performing a Storage Rollback can
affect performance. Vary the size to determine the optimal setting for your system.
6. Use the drop-down menu to select the appropriate number of threads in the Number of Threads
field. The default number of threads is four.
Note Depending on the number of CPUs available on your system and the type of volume on
which the file system is located, this default setting may specify too few or too many
threads.