Background documentationrecover_check Locate this document in the navigation structure


Use this command to check whether Database Manager can properly access the specified data carrier and read the data there.

You can use this DBM command to check if access to a backup tool is functioning, for example.

This DBM command is executed irrespective of the functions running on the database. However, it might cause a temporary loss of performance in the database.

Note Note

The backup specified is just checked, not restored.

End of the note.



recover_check <medium_name> <type> [EBID <ebid_list>] [<nnn>] [UNTIL <date> <time>]

<ebid_list> :: = <external_backup_ID> | <external_backup_ID>,<external_backup_ID>,...





Name of the backup template


Type of backup. Possible values are: DATA | PAGES | LOG

DATA: complete data backup

PAGES: incremental data backup

LOG: log backup


For log backup only:

version of the backup on the data carrier,

only relevant for a data carrier of the FILE type

UNTIL <date> <time>

<date> ::= <yyyymmdd>

<time> ::= <hhmmss>

For log backup only:

exact time (year, month, day, hour, minutes, seconds) up to which you want to check


List of external backup IDs

Seperate several backup IDs using commas.

If backup IDs contain spaces, enclose the list in double quotation marks.


Name under which the backup is known to the external backup tool (only for checking a backup, which was created with a backup tool of another provider)



Returncode <value>


Values for the Reply Fields






Start time of the backup


Name of the database computer


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


Number of data carriers used


Name of the backup template


File or device name


Error message text

See also:

Messages documentation


Backup ID

Is Consistent

Only for data backup: Backup is internally consistent

First LOG Page

For data backup: First page of the log backup to be read

For log backup: First page saved in the log area

Last LOG Page

For log backup only: Last page saved in the log area

DB Stamp 1 Date DB Stamp 1 Time

Time stamp for the first page of the log backup

DB Stamp 2 Date DB Stamp 2 Time

Time stamp for the last page of the 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 that belong together

If an error occurs you will receive a reply with the following information:

Reply in the Event of an Error




Error Message Number

See: Messages documentation


Description of the error


Cause of error

The following errors may occur:


Error Message Number

Error message text



ERR_TOOLCHK: the external backup tool was not found

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


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

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


ERR_PREPARE: prepare of the backup operation failed

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


ERR_DBREQ: cannot start database kernel request

The database was unable to start the backup.


ERR_TOOLREQ: cannot start external backup tool correctly

The backup tool could not be started correctly.


ERR_OPCHK: cannot check state of backup operation

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


ERR_POSTOP: cannot finish backup operation correctly

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


ERR_BACKUPOP: backup operation was unsuccessful

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


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.