I am surprised that a RESTORE REBUILD does not control the availability of backups before starting the operation.
For example, let's assume this sequence:
- FULL backup
- FULL incremental backup
- FULL tablespace backup
- FULL backup is removed, DBA is not aware about this situation
==> The restore rebuild will proceed and your database is scratched.
Why not testing first backups availability to avoid letting DB in restore pending status ?
Thanks for your detailed long answer.
For a very long time, I have considered DB2 privileging no data loss, and today, from this REBUILD perspective (or RESTORE INCREMENTAL automatic), we must be carefull before attempting such a RESTORE.
Now that said, if we regularly do backups, this situation to loose the DB should not happen, but this problem might anyway arise. I don't see why a RFE should be needed here to ask for better security. When not using REPLACE EXISTING, you ask the question if we really want to scratch our DB files, that's good, but I would prefer a warning like : attention do you have all you backup files ?