IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Ability to add columns to DB2 z/OS tables without impacting IDAA or incremental update

Currently, adding a column to a DB2 z/OS table that is using IDAA with incremental update involves:

1) Adding the column in DB2 z/OS
2) Stopping replication for all IDAA tables
3) Dropping the affected table from IDAA
4) Adding the affected table back to IDAA
5) Restarting replication, which first forces a full reload of the affected table.

I am requesting that this process be simplified to:

1) Add the new column to the DB2 z/OS table

That's it. There should be no need to drop/add tables to IDAA. There should be no need to manually stop/start replication, and there should be no need to do a reload.

With CDC from DB2 z/OS to other types of target databases, we accomplish this with the following steps. IDAA should automate most of this. It does require ADDCOLUMNISSCHEMACHANGE=YES and ONSCHEMACHANGE=STOP parameters for CDC z/OS.

1 - Applications touching the table to modified are quiesced. (Manual process)
2- The add column is performed to the DB2 z/OS table. (Manual process)
3- When CDC sees the add column in the DB log, it stops replication for the CDC subscription. (Automatic within CDC today)
5 - The target table is altered to add the same column (IDAA should automate this)
6 - A refresh of the CDC metadata for the source and target tables is performed. (this function is available in the CDC access server java API and this should be automated by IDAA)
7 - The subscription is restarted. (Should be automated by IDAA).
8 - Applications are allowed back in. (Manual process - but I would suggest that the subscription start message could be trapped by the customer to know when everything is ready for application access)
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 18 2018
  • Future consideration
Idea Priority High
Customer Name State Farm
  • Attach files

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 "anonymous@euprivacy.out" 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