After upgrading from DB2 V12 FL100 to DB2 V12 FL510, the DDL generated for tables containing TIMESTAMP columns has "WITHOUT TIMEZONE" clause in them.
1. Is this the default behavior for Db2 12 FL510?
2. Is there any workaround to go to the old behavior?
3. Is there are any implications or considerations customer should be aware of regarding this clause in their existing processes?
1. In February of 2019, Broadcom published a PTF for KEY LABEL toleration support (SO07379, with companion PTFs SO07378, SO07380, SO07381, SO07382, SO07383 and SO07384). This PTF permanently changed the format of the DDL that is generated on V12R1M502 and later DB2 subsystems to include the 'WITHOUT TIME ZONE' clause on TIMESTAMP columns that are not defined as 'WITH TIME ZONE'. For Db2 12 FL510 and later version, this is the new default
2. There is no work around to get back to the old behavior.
3. This clause is the DB2 default for a TIMESTAMP column not defined as 'WITH TIME ZONE', so there should be no difference in DB2 or application behavior, except for the fact that this clause is now explicitly specified in the DDL.