Currently, the Cloning tool does not Unload/Load tables that have RI defined on them. This is despite the fact that these tables become eligible for Unload / Load due to legitimate reasons like Source Target Mismatch where Source defined as a Simple Tablespace under v5 and the db2 v12 does not allow the Target tablespace to be created as a Simple Tablespace.
The Corrective measure is to drop the Source and recreate it under v12 in Production - this is not a viable option due to the outage caused.
All 5 Customer Systems at Duke are impacted by this issue as they all use RI.
|Who would benefit from this IDEA?||All Clients using the IBM Cloning tool whose typical usage is to move data from 24x7x365 environments (Prod) to a Target that is not a 24x7x365 (Dev) will be benefited.|
How should it work?
Proposed Solution is to enhance the functionality of the Cloning tool by adding a new Parm (Unload-Load-Tables-With-RI) that the user can set to YES/NO - the tool can check the flag and proceed with Unload/Loading the tables when set to YES. And then Warn the users that Tables may be in Check-Pending post the Load.
The benefit will be that the entire set of tablespaces will be cloned using the tool instead of time consuming interventions.
The wok around is to exclude the Simple TS and perform an Unload / Load the table outside of the tool, which then needs a backing out of the Log to keep the Simple tablespace in SYNC with the rest copied using the tool.
|Priority Justification||Our next Copy of Production will be done on 6/27 and like to use the Cloning tool|
|Customer Name||Raman Bharde from Duke Energy|
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