Restore Database Dialog
You can set up database recovery options on the Restore Database dialog.
For more information, see
Restore a Database (see
Restore a Database).
This dialog contains the following pages:
• General
• Options
• Output Log
General Page
The General page lets you specify the following restore options:
Recover From Files
Lets you choose from the following recovery options:
Recover from Files
Specifies that the database should be recovered from the checkpoint files
Do not Recover from Files
Specifies that the database should not be recovered from the checkpoint files
Default: Recover from Files
Current Backup
Specifies the recovery should be made from the current backup
Previous Backup
Specifies that the recovery should be made from a previous backup set. Click Backup Set to choose the backup to recover.
Default: Current Backup
Apply Journaling
Lets you choose from the following journaling options:
Recover with the Journal
Specifies that the database should be recovered with the journal
Do not use the Journal
Specifies that the database should not be recovered with the journal
Default: Recover with the Journal
Tables
Lets you choose from the following tables options:
All Tables
Specifies that all the tables in the database backup be recovered
Specify Tables
Specifies that only specific tables be recovered from the database backup. Click the Tables button to select the tables to recover.
Default: All Tables
Inhibit Automatic Recovery of Secondary Indexes
Inhibits automatic recovery of secondary indexes. All secondary indexes will be marked inconsistent. The base table cannot be accessed until the secondary indexes are rebuilt or dropped.
This option is available only if you specify particular tables to recover.
Continue Processing Journal Records on Error
Note: This option is invalid for Actian Vector or for database-level recovery. This option is available only if you specify particular tables to recover.
Continues processing journal records if an error occurs, but does not apply subsequent records for the table. The table is removed from the table list and processing continues. The table or index will be marked inconsistent at the end of recovery. The database will also be marked inconsistent to bring to your attention the errors that occurred during recovery. Choose this action for secondary indexes (which can be rebuilt) or if the table can be rebuilt from another source.
If this option is not specified and an error is encountered, all tables being recovered are marked inconsistent and recovery terminates.
Note: This option does not force continuation of an invalid recovery. The recovery process is terminated immediately if an invalid table—for example, a view, system catalog, Enterprise Access table, nonexistent table, or a table for which recovery is disallowed—is specified.
Verbose Mode, Print Information as the Restore Proceeds
Recovers the database from the journal in verbose mode, which provides diagnostic information about all operations executed during the recovery process.
Options Page
The Options page lets you specify the following options:
Wait for Database
Specifies whether to wait for the database to be free (not in use) before performing the recovery
Default: Don’t Wait
Parallel Restore # of Locations
This option is invalid for Actian Vector.
For multi-location databases, recovers the number of locations at a time from disk.
Default: 1
Perform an Incremental Restore
This option is invalid for Actian Vector.
Indicates an incremental recovery.
When you specify this option with Recover from Files and Do not use the Journal (General page), the backup is restored, and recovery marks the database inconsistent with inconsistency code INCR_RFP. While the database is inconsistent (INCR_RFP), you can still connect and perform read-only operations.
When you specify this option with Do no Recover from Files and Recover with the Journal (General page), the recovery applies all new journal files that have been moved into the journal directory.
If Bypass the Rollback Phase is also specified, any open transaction context is written at the end of the last journal file processed.
Before processing new journals, open transaction context is restored from the previous incremental roll forward.
If Bypass the Rollback Phase is not specified, after journal processing has finished, any open transactions are rolled back. The database will be marked consistent and updatable. This option should be specified when you have finished the incremental recovery.
Note: Incremental recovery requires that all journals since the last checkpoint be present. For example, if you apply a batch of journal files and then delete the previous batch of journal files, incremental recovery with rollback may fail.
Default: unchecked
Bypass the Rollback Phase
This option is invalid for Actian Vector.
Bypasses the rollback phase of recovery and leaves the database in the exact state described by the journal files.
Default: unchecked
Force Journaling Enablement
This option is invalid for Actian Vector.
Forces journaling enablement, if recovery with journaling is attempted on a database that has journaling disabled.
Default: unchecked
Print Statistics About the Recovery Operation
Prints statistics about the recovery operation.
Default: unchecked
Ignore Journal Record Errors
Ignores any errors that occur during the processing of journal records, and applies subsequent records for the table. The table will be marked inconsistent at the end of the recovery. The database will also be marked inconsistent to bring to your attention the errors that occurred during recovery. Choose this action when the table cannot be rebuilt from another source and you want to try to recover as much data as possible.
Default: unchecked
Size of the Local Cache
Specifies the size of the local cache that recovery allocates, in number of buffers. Default values are 256 buffers.
If you specify 0 for the 4K, 8K, 16K, 32K, or 64K buffers, 256 buffers are allocated.
Output Log Page
When you click OK on the Restore Database dialog, the Output Log page displays the contents of the output log as the database is restored.