|The following option will be added to the syntax of the RESTORE DATABASE |command after the TABLESPACE/TABLESPACE ONLINE/HISTORY FILE options:
|>>-+-------------------------+--------------------------------->< | '-INCREMENTAL--+-------+--' | '-ABORT-' |
|The parameter descriptions will be added as follows: |
|
|The following examples will also be added:
|The following is a sample weekly incremental backup strategy with a recoverable |database. A full backup is scheduled once per week, a delta every day, plus |an incremental mid-week:
| (Sun) backup db kdr use adsm | (Mon) backup db kdr online incremental delta use adsm | (Tue) backup db kdr online incremental delta use adsm | (Wed) backup db kdr online incremental use adsm | (Thu) backup db kdr online incremental delta use adsm | (Fri) backup db kdr online incremental delta use adsm | (Sat) backup db kdr online incremental use adsm
|For a manual database restore of images created above on Friday morning, |issue the following commands:
| restore db kdr incremental taken at (Thu) | restore db kdr incremental taken at (Sun) | restore db kdr incremental taken at (Wed) | restore db kdr incremental taken at (Thu)
|The second paragraph in the section entitled "DB2 Data Links Manager Considerations" |should be replaced with:
| If one or more Data Links servers are configured for the database, | the restore operation will succeed, even if a Data Links server is not available. | When the Data Links server restarts, restore processing will be completed | on that Data Links server before it becomes available to the database again. | NOTE: If a database restore operation is still waiting for an unavailable | Data Links server, any subsequent database or table space restore operations | will fail.