Mimer SQL Reference Manual TOC PREV NEXT INDEX

Mimer Developer Site



Restores a databank from a backup of LOGDB or from the information currently in LOGDB.




This form of ALTER DATABANK is used to recover a databank in the event of it being damaged or destroyed. It is possible to use this SQL statement to restore the databank from information contained in the log records for the databank held in the current LOGDB or from a LOGDB backup, refer to of the Mimer SQL System Management Handbook for details on Backup and Restore.

The recovery operation must start from a usable backup copy of the databank file, which has been created using the host file system backup or from a backup taken using CREATE BACKUP.

Once the restored databank file is in place, ALTER DATABANK is used to bring the databank up to date by applying any updates made to it since that copy of the databank file was taken. The updates may have been recorded in one or more backups of LOGDB and the latest updates will be contained in the log records in the LOGDB system databank.

The syntax options are:


Only the creator of the databank or an ident with BACKUP privilege (e.g. SYSADM), may use the ALTER DATABANK RESTORE statement to restore it.

If the databank does not have LOG option, there will be no operations recorded in LOGDB.


It is possible to restore a databank that has been set offline.

The recovery operations performed using ALTER DATABANK RESTORE can only be applied to a copy of a databank file which has been placed in the original file location used by the databank.

If the copy of the databank file must be restored to a new location for some reason (e.g. a disk has been lost), then ALTER DATABANK is first used to change the databank file location.

Standard Compliance

The ALTER DATABANK RESTORE statement is a Mimer SQL extension.

Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40
Mimer SQL Reference Manual TOC PREV NEXT INDEX