recover_check 
Use
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.
The backup specified is just checked, not restored.
Prerequisites
● You have the server authorization Backup.
● You have opened a service session (see: service_connect).
Syntax
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: complete data backup PAGES: incremental data backup LOG: log backup |
<nnn> |
Only for log backup: 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> |
Only for log backup: exact time (year, month, day, hour, minutes, seconds) up to which it is to be checked |
<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> |
Only for checking a backup that was created with a backup tool of another provider: name under which the backup is known to the backup tool. |
Successful Reply
OK
Returncode <value>
Date [<value>]
Time [<value>]
Server [<value>]
Database [<value>]
Kernel Version [<value>]
Pages Transferred [<value>]
Pages Left [<value>]
Volume Count [<value>]
Mediumname [<value>]
Location [<value>]
Errortext [<value>]
Label [<value>]
Is Consistent [<value>]
First LOG Page [<value>]
Last LOG Page [<value>]
DB Stamp 1 Date [<value>]
DB Stamp 1 Time [<value>]
DB Stamp 2 Date [<value>]
DB Stamp 2 Time [<value>]
Page Count [<value>]
Devices Used [<value>]
Database ID [<value>]
Max Used Data Page [<value>]
Values for the Reply Fields
Value |
Description |
Date |
Date |
Time |
Time |
Server |
Name of the database computer |
Database |
Name of the database instance |
Kernel Version |
Version of database software |
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 |
Label |
Backup ID |
Is Consistent |
For data backup only: backup is internally consistent |
First LOG Page |
For data backup: first page of log backup to be imported For log backup: first page saved in log |
Last LOG Page |
For log backup only: last page saved in log |
DB Stamp 1 Date |
Time stamp for first page of log backup |
DB Stamp 2 Date |
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 that belong together |
Max Used Data Page |
Highest page number assigned (indication of minimum database size when backup is imported) |
Reply in the Event of an Error
ERR
<err_code>, <err_description>
[<extended_description>
Values for the Reply Fields
Value |
Description |
<err_code> |
Error Message Number See also: Documentation, |
<err_description> |
Description of the error |
<extended_description> |
Cause of error |
Messages
The following errors may occur:
<err_code> |
<err_description> |
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 an external backup tool |
The specified backup template cannot be used with a 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 instance was unable to start the check. |
-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 instance or the backup tool. |
-24921 |
ERR_POSTOP: cannot finish backup operation correctly |
Although the backup was successful, the post-processing steps required could not be performed. |
-24920 |
ERR_BACKUPOP: backup operation was unsuccessful |
The check failed due to a problem in the database or the backup tool. |
-24919 |
ERR_CLEANUP: cannot clean up correctly after backup operation |
Although the check was successful, the system resources used during the check could not be released again. |