IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

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

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Planned for future release
Created by Guest
Created on Nov 5, 2021

Temporal Base Table SQLOUT INSERTS have generate always columns as part of the insert

The timestamp columns supporting temporal should not be part of the INSERT. Also anytime a generate always column is excluded as it should have been in this run, columns must be added to the INSERT statement.

--UNDO SQL FOR SUBSYSTEM: DAA1

--LRSN:00DA7AEA46E5238BB600 URID:000000006E00700E0F73

--#00000001 *UNDO DELETE* DATE/TIME:2021-10-18/06.53.42

INSERT INTO

"TOTC"."ECRN"

VALUES(

'KA0 '

,+287

,'2020'

,'1'

,'F'

,'KA0REMIT-FED '

,'2021-10-14-06.25.15.511368025000'

,'9999-12-30-00.00.00.000000000000'

,'2021-10-14-06.25.15.511368025000'

);

SET CURRENT SQLID='TOTC';

CREATE TABLE TOTC.ECRN

(CO_C CHAR(6) FOR SBCS DATA NOT NULL,

EMP_FILE_NB DECIMAL(9, 0) NOT NULL,

CAL_4_DGT_YR_D CHAR(4) FOR SBCS DATA NOT NULL,

QTR_NB CHAR(1) FOR SBCS DATA NOT NULL,

REMT_TYP_C CHAR(1) FOR SBCS DATA NOT NULL,

REMT_NB CHAR(30) FOR SBCS DATA NOT NULL,

SYS_BEG_D TIMESTAMP (12) WITHOUT TIME ZONE NOT NULL

GENERATED ALWAYS AS ROW BEGIN,

SYS_END_D TIMESTAMP (12) WITHOUT TIME ZONE NOT NULL

GENERATED ALWAYS AS ROW END,

TRANS_ID_D TIMESTAMP (12) WITHOUT TIME ZONE NOT NULL

GENERATED ALWAYS AS TRANSACTION START ID,

PERIOD SYSTEM_TIME (SYS_BEG_D, SYS_END_D),

CONSTRAINT CO_C

PRIMARY KEY (CO_C,

EMP_FILE_NB,

CAL_4_DGT_YR_D,

QTR_NB,

REMT_TYP_C))

IN DTOTCEM1.SEMECRN

PARTITION BY SIZE

AUDIT NONE

DATA CAPTURE NONE

WITH RESTRICT ON DROP

CCSID EBCDIC

NOT VOLATILE

APPEND NO ;

COMMIT;

Needed By Quarter
  • Guest
    Dec 17, 2021

    We just ran into the same situation for a production recovery following a bad spufi update ad-hoc that ran on a temporal table. we needed to recover the updates. although producing the Undo SQL is how we thought we could resolve quickly, we found out that we would need to modify the thousands of statements to remove the TRANSI_ID_D. We had to try to find a synch point to recovery to, since the user made no backup prior to their update.

    We have used the undo several times in the past and it saved us big time. but this time it was useless. Temporal Tables are REQUIRED by IBM to contain this TRANS_ID_D generated always timestamp column. So although IBM is treating this AHA as an enhancement, We see this as a DEFECT! All IBM tools should support all types of DB2 objects that IBM introduces. Temporal has been around for a while and has since matured. Why wasn't log analyzer tested for support of temporal tables for undo/redo sql. they would have quickly found out that IT DOES NOT WORK!. bottom line, the tools should support all DB2 objects, no different than how it supports LOB , XML, etc. it should support TEMPORAL tables. It's not like we had an option on whether or not to create this GENERATED ALWAYS TIMESTAMP for these types of tables, it is a REQUIREMENT.


    I am hoping this gets resolved sooner than later. THIS IS A DEFECT!!!!

  • Guest
    Nov 15, 2021

    This issue is not restricted to temporal base tables. It also happens to with generated UNDO SQL by log analyzer for any table with generated always columns.

    The issue is described without a solution. I assume the "idea" for log analyzer is to have a parameter to not generate these columns in the insert in the generated sql. correct?