recover_check

You check whether the 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 instance.

Note Note

The backup specified is just checked, not restored.

End of the note.

Prerequisites

You have the server authorization Backup.
You have opened a service session (see: service_connect).

Structure

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

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

Options
Option	Description
`<medium_name>`	Name of the backup template
`<type>`	Type of backup. Possible values are: `DATA \| PAGES \| LOG` `DATA`: complete data backup `PAGES`: incremental data backup `LOG`: log backup
`<nnn>`	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
`<ebid_list>`	List of external backup IDs If the list contains several backup IDs, then these must be separated by commas. If backup IDs contain spaces, the list must be enclosed in double quotation marks.
`<external_backup_ID>`	Name under which the backup is known to the external backup tool (only for checking a backup that was created with a backup tool of another provider)

Result

OK

Returncode <value>

...

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

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

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.