We want to avoid submitting a job that attempts to recover a table (using advanced recover) if the table is unrecoverable, as this may lead to a situation where we have lost the table without being able to restore it.
This should also be the case when we are not utilising the schema level repository.
|Who would benefit from this IDEA?||Anybody doing mass recovery without using the schema level repository.|
How should it work?
Ideally it should be possible to determine whether a table is unrecoverable when you are not using schema level repository, and then issue a warning or error when attempting to recover it.
|Priority Justification||We do not feel comfortable performing mass recovery when we risk dropping objects that are not recoverable. I.e. we cannot use the tool untill this is fixed.|
|Customer Name||JN Data|
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