Rolling back to a Storage Checkpoint

You can roll back the entire database to a Storage Checkpoint.

The GUI does not automatically roll back any logs associated with a Storage Checkpoint.

See "Guidelines for DB2 Recovery" in the Veritas Storage Foundation for DB2 Administrator's Guide.

You must be the Database Administrator to perform Storage Rollback operations. For an online Storage Rollback, the instance should be running, but the database must be in archive mode (either active or inactive). For an offline Storage Rollback, the instance can be running or inactive, but the database must be inactive.

Storage Checkpoints can only be used to roll back files that are damaged due to a software error or a human error (for example, accidental deletion of a table). Because Storage Checkpoints reside on the same physical disks as the primary file system, when a file is corrupted due to a media failure, the file on the Storage Checkpoints will not be available either. In this case, you need to restore files from a tape backup.

After the files are rolled back, you may need to follow the recovery procedure described in your DB2 manuals to recover the database before the database can be used.