The database manager can optionally call a user exit program to backup and
restore a database, to archive and retrieve log files, or both. Calling
a user exit program for one pair of tasks (backup and restore or archive and
retrieve) does not require that a user exit program be used for the other pair
of tasks. For example, if you archive and retrieve logs with a user
exit program, you are not required to back up and restore databases with a
user exit program.
The database manager can call a user exit program with one of the following
- The BACKUP DATABASE utility calls a user exit program when you specify
0: as the target drive parameter from the command line
processor, or U as the media type on the API call. Refer to "Backing Up a Database" for additional information about backing up a database.
- The RESTORE DATABASE utility calls a user exit program to retrieve
database files that were previously stored by BACKUP DATABASE calling a user
exit program. The RESTORE DATABASE utility calls a user exit program by
specifying 0: as the source drive parameter from the command
line processor, or U as the media type on the API call.
Refer to "Restoring a Database" for additional information about restoring a database.
- Archive and Retrieve
- The database manager archive and retrieve functions call a user exit
program to store and retrieve log files and to manage the location of archived
log files if the database configuration parameter, userexit, is
on. Using a user exit program to archive and retrieve files enables a
database for roll-forward recovery (refer to "Rolling Forward Changes in a Database").
|Note:||The userexit configuration parameter applies to the archiving and
retrieving of log files only.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]