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:
  • 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.

Additional Information:
  • The shorter URL for this site is:

  • To view our 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.


CCB occasionally received SQLCODE -20528. As stated in DB2 CODES manual, this can occur while two transactions trying to update a row in system-period temporal table closely. A row being moved to history table can have sys_start higher than sys_end that results in the error. Customer will need to resubmit job after the failure.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 15 2018
  • Not Under Consideration
Idea Priority Medium
Customer Name IBM China for CCB CHINA
  • Attach files
  • Admin
    Janet Figone commented
    31 Jul 11:19pm

    Hi Jeff, I have alerted our developer of your comment and asked for a response to your question.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    3 Jun 02:17pm

    We are trying to create an audit trail for updates to a critical table, and making it a system-period temporal table seemed to be the perfect solution without having to change any application code. However these -20528 errors are making this option unusable.

    I don't understand the comment that "the product decision is to be different from LUW". Is DB2 for z/OS implementing a different way to solve this problem?

    Honestly, it would seem to make more sense for the row-begin column to be set to the actual time of the update, rather than the time of the start of the unit of work. Then you could see the actual order that the rows were updated. You would still have the transaction start column to identify rows updated in the same transaction.

  • Admin
    Janet Figone commented
    13 Feb 01:11am

    Thank you for submitting this enhancement. The product decision is to be different from LUW therefore this enhancement is not under consideration.

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