This starts a roll forward of the given log. The log may have
been produced by normal transaction logging, backup or crash dump.
Logs may not be transferred between databases and thus cannot be
rolled forward anywhere except on the database that generated
This function is for example useful after restoring a backup. It
should be called for each archived transaction log produced since
the backup, including and starting with the one that was current
when the backup was made.
The operation blocks until the roll forward is complete. Other
clients are not affected.
The above sequence of commands makes a checkpoint and starts
logging subsequent transactions into new.log. The backup statement
makes bak.log, which represents the state prior to starting
new.log. The shutdown statement makes a new checkpoint and marks
new2.log as the log file to be used for logging transactions after
the database restarts. The database server exits at the completion
of the SHUTDOWN statement.
These statements executed on an empty database will recreate the
state in effect after the last transaction to commit before the
SHUTDOWN statement of the previous example.