You check that the backup is consistent and complete. This command is executed independently of the current database instance functions but can adversely impact database instance performance temporarily.
You have the DBM operator authorization Backup.
You have opened a service session.
recover_check <medium> <type> [ExternalBackupID <external_backup_ID>] [<nnn>] [UNTIL <date> <time>]
<medium> |
Name of the backup medium; this must be defined beforehand (Defining or Changing a Backup Medium) |
<type> |
Type of Backup: DATA (Complete data backup), PAGES (Incremental data backup) or LOG (Log Backup) |
ExternalBackupID <external_backup_ID> |
To check a backup created with an external backup tool, enter a backup ID name that the external tool will recognize. |
<nnn> |
Actual backup version on the backup media that is being checked; relevant only for media of type FILE |
UNTIL <date> <time> |
For log backups you can enter an exact time up to which the log backups are to be checked. |
The backup specified is just checked, not restored.
OK<NL>
Returncode
<value><NL>
Date
[<value>]<NL>
Time
[<value>]<NL>
Server
[<value>]<NL>
Database
[<value>]<NL>
Kernel Version
[<value>]<NL>
Pages Transferred
[<value>]<NL>
Pages Left
[<value>]<NL>
Volume Count
[<value>]<NL>
Mediumname
[<value>]<NL>
Location
[<value>]<NL>
Errortext
[<value>]<NL>
Label
[<value>]<NL>
Is Consistent
[<value>]<NL>
First LOG Page
[<value>]<NL>
Last LOG Page
[<value>]<NL>
DB Stamp 1 Date
[<value>]<NL>
DB Stamp 1 Time
[<value>]<NL>
DB Stamp 2 Date
[<value>]<NL>
DB Stamp 2 Time
[<value>]<NL>
Page Count
[<value>]<NL>
Devices Used
[<value>]<NL>
Database ID
[<value>]<NL>
Max Used Data Page
[<value>]<NL>
Date |
Date |
Time |
Time |
Server |
Name of the database server |
Database |
Name of the database instance |
Kernel Version |
Database kernel version |
Pages Transferred |
Number of pages transferred |
Pages Left |
Number of pages still to be transferred |
Volumes |
Number of backup media used |
Medianame |
Name of the backup medium |
Location |
File or device name |
Errortext |
Error message text |
Label |
|
Is Consistent |
For data backup only: 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 |
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 saved |
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 |
Maximum page number (indication of minimum database size when backup is imported) |
If an error occurs during the process, you will receive a reply in the following format:
ERR<NL>
<errcode>, <err_description><NL>
[<extended_description><NL>]
<errcode> |
Error message number See also: Messages |
<err_description> |
Description of the error |
<extended_description> |
Cause of the error |
The following errors may occur:
<errcode> |
<err_description> |
Explanation |
-24927 |
ERR_TOOLCHK: the external backup tool was not found |
The external 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 medium specified cannot be used with the backup tool the medium name refers to (Defining and Changing a Backup Medium). |
-24925 |
ERR_PREPARE: prepare of the backup operation failed |
The preparations necessary to use the backup tool were not made 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 with the database or the backup tool. |
-24919 |
ERR_CLEANUP: cannot clean up correctly after backup operation |
Although the check was successful, the temporary system resources that were used could not be freed up again. |