rollforwarddb(1sql)
Name
rollforwarddb − recover an ULTRIX/SQL database from the last checkpoint and the current journal.
Syntax
rollforwarddb [options] [ dbname]...
Description
The rollforwarddb command recovers the specified database or databases from the last checkpoint and current journal files. The recommended procedure is to recover the last checkpoint and then recover from the journal (see Examples). All the checkpoint and journal files that are required to recover the specified databases must be on line when the rollforwarddb command executes. If no databases are specified, all databases for which you are the DBA are affected. All databases in the ULTRIX/SQL system can be recovered if the ULTRIX/SQL system administrator executes rollforwarddb with the −s option.
Options
+c|−c
Recover/do not recover the database from the last checkpoint. The default is +c.
+j|−jRecover/do not recover the database from the journal. The default is +j.
−mdevice
Recover the checkpoint from the specified tape device rather than from disk (the default). Use this option if you have written to tape the checkpoint from which you want to restore the journal.
−sInvoke ULTRIX/SQL superuser status for system-wide access to any database. You must be the ULTRIX/SQL system administrator to use this option.
−uusername
Recover the database as though you are logged in as user username. Only the DBA for the database or the ULTRIX/SQL system administrator can use this option.
−vRecover the database from the journal in verbose mode, which provides diagnostic information detailing all operations executed during the recovery process. The default is not to provide this information.
+w|−w
Wait/do not wait for the database to be free. The default is −w. You can apply +w only if standard input is from the terminal; in other words, ULTRIX/SQL does not wait for a database to be available if rollforwarddb executes in batch mode. The rollforwarddb command locks the database because errors can occur if the database is active while the rollforwarddb command is running. If a database is busy and −w is in effect, the rollforwarddb command reports that the database is unavailable and proceeds to the recovery operation for the next database, if any. If a database is busy and +w is in effect, the rollforward command waits until that database is available and recovers it before attempting to recover the next database (if any).
Restrictions
Only the database administrator, who created the database, or the ULTRIX/SQL system administrator (if the −s or −u option is specified) can run the rollforwarddb command on a database.
Examples
Recover the empdata database from the last checkpoint and journal, specifying that complete diagnostic information be displayed:
rollforwarddb -v empdata
Recover all databases for which you are DBA, specifying that complete diagnostic information be displayed:
rollforwarddb -v
Recover the empdata database from a checkpoint on tape (device special file /dev/rmt0h ) and then apply the journal:
rollforwarddb +c +j -m/dev/rmt0h empdata
Files
$II_CHECKPOINT/ingres/ckp/default/dbname
Default directory for checkpoint files associated with dbname. The default location ii_checkpoint is mapped to this directory.
$II_JOURNAL/ingres/jnl/default/dbname
Default directory for journal files associated with dbname. The default location ii_journal is mapped to this directory.