This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
The "Table 1." provides an official list of object tyep characteristics that must match between the source and target.
As a DBA who uses "redirected recovery" functionality, I have written SQL to query and compare the objects as described in the Db2 catalog.
This provides ME (the DBA) with confidence that the objects are sufficiently identical and my "redirected recovery" will work.
It turns out that RECOVER has been enhanced by IBM for "redirected recovery" to do it's own TABLESPACE and INDEXSPACE SCHEMA comparison.
If RECOVER discovers a difference between the source and target then the difference is reported with
DSNU1566I (to say the tablesapce or indexspace is different)
DSNU1567I (to say the specific thing that is different in the object)
My request for enhancement is to add a new keyword option for RECOVER when doing redirected recovery. The keyword tells RECOVER to do schema comparison only and stop. Do NOT do the recovery into the target.
This new keyword would provide an easy way to confirm and validate that the objects are sufficiently identical for actual redirected recovery without doing the actual recovery.
the section "recover-from-multi-spec" could be updated - after "torba" - to allow new optional key word of 'CHECKSCHEMAONLY'
TABLESPACE sourcedb.ts1 FROM sourcedb.ts1
TABLESPACE targetdb.ts2 FROM sourcedb.ts2
TORBA X'00000000448ED0347D31' CHECKSCHEMAONLY
The benefit is that RECOVER can do official schema comparison and I do not have to write or maintain my own big SQL to compare objects in the catalog (as per my interpretation of the "Table 1." described above).
For example, I have a scenario where I use redirected recovery today. At month-end I use redirected recovery to put a copy of some month-end data into another database. We can then run very long running reports in the target while the source/prod continues with normal updates.
I am paranoid that my source and target db might get out of sync during the month..
> perhaps parition limits change. or something goes multi-dataset and I did not realize. or some other thing happens after a reorg...
So I run daily SQL to compare the objects between the two db.
It would be nice to run a daily redirected RECOVER with CHECKSCHEMAONLY so I have more confidence the objects remain identical.
Another example is just when I might want to do one off redirected recovery of several objects to another db. I could use CHECKSCHEMAONLY to quickly confirm the objects are identical or not.
Of course, the implementation or keyword of CHECKSCHEMAONLY can be changed by IBM to whatever is appropriate. IBM can decide. CHECKSCHEMAONLY is just my quick idea.
Do not place IBM confidential, company confidential, or personal information into any field.