Background documentationdb_activate RECOVER Locate this document in the navigation structure

 

You initialize data and log volumes of the current database instance and import the data backed up in a complete data backup into the database instance. All the data previously contained in the current database instance is overwritten.

This command is also used to create a copy of a database instance, such as is required for the creation of a standby database instance, for example.

Unlike the DBM command for recovering the database instance (see: recover_start) the db_activate RECOVER command deletes all catalog information and application data, as well as all entries in the log area of the database instance. The complete data backup is then imported and the database state it contains is recreated.

When you import the backup you overwrite all the original database user data of the destination instance with the data of the source instance. This is particularly significant if the source database from which the backup was created is different to the destination database into which the backup is imported. To continue working with the destination database instance, and in particular to load the system tables after importing the backup, you require the user data of the database system administrator of the source database instance. Only with this user data can you completely restore the data in the destination database instance. The DBM operator data of the destination database instance is retained.

If you used another provider’s backup tool to make the backups to be imported, you must use that tool to recover the database instance with initialization.

Once db_activate RECOVER has been executed, information on the recovery is displayed. This only happens when the backup has been completely imported or the process was interrupted. For this reason, the response to this DBM command can take a long time.

Note Note

If the automatic log backup was activated before the recovery was started, it is not reactivated automatically after the recovery. To reactivate the log backups, execute the DBM command for activating automatic log backup (see: autolog_on).

End of the note.

Prerequisites

  • You have the server authorization Recovery.

  • The database instance is in the ADMIN operational state.

  • You have opened a database session (see: db_connect).

Structure

db_activate RECOVER <medium_name> DATA [ExternalBackupID <external_backup_ID>] [AUTOIGNORE]

Options

Option

Description

<medium_name>

Name of the backup template that refers to the data carrier or the group of parallel data carriers from which the backup is to be imported.

DATA

Type of backup to be imported is DATA (complete data backup)

You only need to specify an entry here if you want to import a data carrier in whose backup template the backup type was not specified.

ExternalBackupID <external_backup_ID>

To restore a backup created with a backup tool, enter the backup ID name known to this tool.

AUTOIGNORE

The operation to restore multiple parallel data carriers is automatically continued by the system when it has finished importing the data from a single data carrier.

Result

OK

...

...

Values for the Reply Fields

Value

Description

Date

Date

Time

Start time for backup

Server

Name of the database computer

Database

Name of the database

Kernel Version

Version of the database kernel

Pages Transferred

Number of pages transferred

Pages Left

Number of pages still to be transferred

Volumes

Number of data carriers used

Medianame

Name of the backup template

Location

File or device name

Errortext

Error message text

See also:

Messages documentation

Label

Backup ID

Is Consistent

Only for data backup: Backup is internally consistent

First LOG Page

For data backup: first page of log backup to be read

For log backup: first page saved in log

Last LOG Page

For log backup only: last page saved in log

DB Stamp 1 Date DB Stamp 1 Time

Time stamp for first page of log backup

DB Stamp 2 Date DB Stamp 2 Time

Time stamp for last page of log backup

Page Count

Total number of pages backed up

Devices Used

Number of backup devices used

Database ID

Database ID used to identify data and log backups which belong together

Reply in the Event of an Error

If an error occurs while you are using a backup tool, you will receive a reply in the following format:

ERR<NL> <errcode>, <err_description><NL> [<extended_description><NL>]

Reply in the Event of an Error

Value

Description

<errcode>

Error Message Number

See: Messages documentation

<err_description>

Description of the error

<extended_description>

Cause of error

The following errors may occur:

Messages

Error Message Number

Error message text

Explanation

-24927

ERR_TOOLCHK: the external backup tool was not found

The backup tool could not be found or has been installed incorrectly.

-24926

ERR_MEDIUMCHK: the medium cannot be used with this external backup tool

The backup template specified cannot be used with this backup tool.

-24925

ERR_PREPARE: prepare of the backup operation failed

The preparations required to use the backup tool could not be completed correctly.

-24924

ERR_DBREQ: cannot start database kernel request

The database was unable to start the backup.

-24923

ERR_TOOLREQ: cannot start external backup tool correctly

The backup tool could not be started correctly.

-24922

ERR_OPCHK: cannot check state of backup operation

Unable to check the status of the database or the backup tool.

-24921

ERR_POSTOP: cannot finish backup operation correctly

Although the backup was successful, the required post-processing steps could not be performed.

-24920

ERR_BACKUPOP: backup operation was unsuccessful

The backup failed due to a problem with the database or with the backup tool.

-24919

ERR_CLEANUP: cannot clean up correctly after backup operation

Although the backup was successful, the system resources used during the check could not be released again.