The automatic incremental restore is useful when you need to restore your database. However, you should consider the limitations of automatic incremental restore when you are deciding how you will recover your database to prevent unnecessary issues.
The following limitations affect automatic incremental restore:
db2 backup db sample —> <ts1>
db2 backup db sample incremental —> <ts2>
db2 rename tablespace from userspace1 to t1
db2 restore db sample tablespace ('t1') incremental automatic taken
at <ts2>
SQL2571N Automatic incremental restore is unable to proceed.
Reason code: "3".
Suggested workaround: Use manual incremental restore.
db2 backup db sample —> <ts1>
db2 backup db sample incremental —> <ts2>
db2 backup db sample incremental delta —> <ts3>
db2 backup db sample incremental delta —> <ts4>
db2 drop db sample
db2 restore db sample incremental automatic taken at <ts2>
db2 restore db sample incremental automatic taken at <ts4>
db2 create db a
db2 create db b
db2 update db cfg for a using trackmod on
db2 backup db a —> ts1
db2 restore db a taken at ts1 into b
db2 backup db b incremental —> ts2
db2 restore db b incremental automatic taken at ts2
SQL2542N No match for a database image file was found based on the source
database alias "B" and timestamp "ts1" provided.
db2 restore db b incremental taken at ts2
db2 restore db a incremental taken at ts1 into b
db2 restore db b incremental taken at ts2