Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Workspace Db2 for z/OS
Created by Guest
Created on Jul 4, 2018

TRIGGERS referencing system temporal tables

Hello,

Since we are in DB2 V10 we use triggers with bi-temporal tables
(system temporal + business temporal table) to implement complex
relational integrity rules that can not be defined using standard
primary/foreign keys. It's related to simple INSERT or
DELETE/UPDATE with FOR PORTION OF BUSINESS_TIME statement.
All of our development was based on recommendation made in
IBM DeveloperWorks document "Managing time in DB2 with temporal
consistency Enforce time-based referential integrity" from July 12, 2012
written by Mr. Matthias Nicola and Mr. Martin Sommerlandt.

In DB2 V10 and DB2 V11 conversion mode, there was no problem.
It was possible to define a trigger referencing a SYSTEM TEMPORAL or
BI-TEMPORAL table in the WHEN clause. Since we are in DB2 V11, we
receive an SQLCODE=-270 each time that the package trigger is rebound.

In DB2 V11, there is a procedure to circumvent this issue,
we have to alter the BI-TEMPORAL table to DROP the VERSIONING,
DROP/CREATE the trigger, add the VERSIONING and finaly REBIND
the TRIGGER PACKAGE with bind option SYSTIMESENSITIVE NO.
Even if this procedure is less obvious than before, it works.

According to IBM, in DB2 V12, this solution will not work anymore and
we will have to review/drop the triggers that are impacted and implement
the RI in the programs that are updating the tables.
This solution will work too but the RI will not be verified if the
update is done via spufi, datastudio, ...
With triggers it was also verified in such cases.
This solution is than a lot less secured, and more difficult to
maintain (one TRIGGER per type of modification vs multiple programs
doing insert/update/delete).

Regards,
Francis Pirotton
  • Admin
    Janet Figone
    Reply
    |
    Oct 31, 2019

    We are pleased to inform you this Aha! Idea (previously RFE 80386) has been delivered in Db2 12 for z/OS Function Level 505. For additional information about FL505 please see our Knowledge Center: https://www.ibm.com/support/knowledgecenter/en/SSEPEK_12.0.0/wnew/src/tpc/db2z_fl_v12r1m505.html