Database Administrator's Guide

Running the Rollback Utility

The ctrdmp utility performs a system rollback as well as dynamic dump recovery. ctrdmp checks the first keyword in the script file. If the first line is !ROLLBACK the script is used for a rollback. If it isn’t, the script is considered a dynamic dump script and used for a dump or a recovery.

Note: As in dump recovery, be sure the particular FairCom Server undergoing the rollback is not running when ctrdmp starts, since ctrdmp is a FairCom Server and the two FairCom DB Servers operating simultaneously interfere with each other. Typically, error TCOL_ERR (537, transaction log collision) is observed under these conditions.

Perform a rollback as follows:

1. Collect ctrdmp, the transaction log files covering the period from the target time to present, and the current log files into a working directory.
2. Start ctrdmp the same way as any program in the environment.
3. When prompted, enter the name of the rollback script file to be used.

The rollback begins automatically and produces a series of messages reporting recovery progress. A message returns when the utility completes a successful rollback.

A successful ctrdmp completion outputs the following message to CTSTATUS.FCS:

DR: Successful Dump Restore Termination

A failed ctrdmp outputs the following to CTSTATUS.FCS:

DR: Dump Restore Error Termination...: <cterr>

where <cterr> is a c-tree error code number.

If for some reason ctrdmp terminates prematurely (for example, a fatal error causes ctrdmp to terminate abnormally), the “Dump Restore Error Termination...” message may not be written to CTSTATUS.FCS. In that case, ctrdmp may have written error messages to standard output or to CTSTATUS.FCS before terminating that explains the premature termination.