We are currently testing DB2 Recovery Expert and our analysis is showing that we can have a very large Recovery Plan that includes objects that may not need reeovery. This might be due to the fact that Recovery Expert is analyzing the DB2 Catalog alone for object relationships and is assuming all related objects must be recovered.
|Who would benefit from this IDEA?||Any DBA that is involved in a recovery scenario and needs to understand why a Recovery Plan could not be built.|
How should it work?
Assuming our analysis above is correct in how Recover Expert determines the total Recovery Plan we are proposing the following:
1) Analysis should also include a review of SYSIBM.SYSLGRNX to determine which objects actually had Ins/Upd/Del or other modification activity
2) Based on the Recovery Plan option chosen the analysis should:
a) Determine the earliest RBA that is required to start the Recovery process
b) For related objects via database RI any object that has not had any Ins/Upd/Del or other modification activity from the start point in a) to the expected end point, should be excluded from the Recovery Plan
c) Examples of a table that would qualify for b) would be an RI Parent table which has a Child table to be recovered but the Parent had no activity. This would be true for a lot of Reference-only tables that very seldom change.
d) Examples of a table that would NOT qualify for b) would be an RI Child table that has no activity but it has a parent table that has had Ins/Upd/Del or other modification activity. In this case the Child table, and any tables further down the chain, need to be included.
e) Any objects that would have been brought into the Recovery Plan via a table qualifying for b) should also be excluded as those objects most likely have nothing to do with the objects actually being recovered.
3) An additional reporting DD should provide a summary of which objects were excluded from the Recovery Plan based on the qualifying rules stated in #2
|Priority Justification||When faced with a recovery situation that may already by its nature be complicated, we can't spend a lot of time determining if there are objects present that have no reason to be involved in the recovery process|
|Client Name||Dave Petronella|
|IBM's success depends on gathering feedback from customers like yourself. Aha Ideas Portal is the third party tool through which IBM Offering Managers gather feedback from customers such as yourself.|
|IBM is a global organization with business processes, management structures, technical systems and service provider networks that cross borders. As such, the information collected through Aha Ideas Portal (Customer Name, Customer Email Address) will be stored by them in the United States, and handled only as per IBM's instructions and policies. Your data (Name and Email Address) will NOT be shared with other IBM customers.|
|In order to safeguard your information in Aha, do not leave your workstation unattended while using this application, log off after using it, and print only if necessary. If you need to make a hardcopy, remember to pick up the print-out immediately, keep it under lock, and destroy it immediately when no longer needed.|
|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 "firstname.lastname@example.org" 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|