Today, Db2 Restore can continue with a subset of tablespaces if e.g. same tablespaces fail to acquire containers. In the end of roll forward completes, but some tablespaces did not complete and remain in 'storage definition pending' and need to have recovery (restore/rollforward) restarted for these tablespaces.
This is expected. By default Db2 prioritizes getting as much of the database up and recovery as quickly as possible.
A configuration option would be helpful to abort restore if tablespace errors occur, similar to DB2_FAIL_RECOVERY_ON_TABLESPSACES_ERROR
|Who would benefit from this IDEA?||Customers who had to restore large databases with a large number of tablespaces|
How should it work?
A Db2 registry (e.g. DB"_FAIL_RESTORE_ON_TABLESPACE_ERROR [CONTINUE|ABORT|CONTINUE_UNCRITICAL]) variable should be provided which allows to configure if a Db2 restore operation should continue (like today) or abort completely. A further option would be helpful to continue just if a restore error occurs on 'non critical' tablespaces (SYSTOOLSPACE, TEMPORARY TABLESPACES etc.).Aborting the first restore, fixing the problem and start the complete restore again could be much faster.
|Priority Justification||Idea is ranked 'High' because of experience many repeated recoveries|
|Customer Name||Heribert Gausmann|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions