To support the creation of a Db2 range-partitioned target table if the source table is a Db2 range-partitioned table and the target table does not exist when creating a Q Subscription.

According to the current design, when the target table does not exist, Q Replication can automatically create the target table based on the source table schema when creating a Q Subscription.

However, Q Replication always creates a normal table, regardless of whether the source table is a normal table or a Db2 range-partitioned table.

The customer would like Q Replication to create a Db2 range-partitioned table when the source table is a Db2 range-partitioned table.

Table example :

CREATE TABLE "TEST"."TABLE1" (
"ID" VARCHAR(64 OCTETS) NOT NULL ,
"CREATE_TIME" TIMESTAMP NOT NULL
)
DATA CAPTURE CHANGES
PARTITION BY RANGE (CREATE_TIME) (
STARTING FROM MINVALUE ENDING ('01/01/2024') EXCLUSIVE,
STARTING FROM ('01/01/2024') ENDING AT ('12/31/2049') EVERY 1 MONTH,
STARTING FROM ('01/01/2050') ENDING MAXVALUE INCLUSIVE)
ORGANIZE BY ROW;

Needed By

Not sure -- Just thought it was cool

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

To support the creation of a Db2 range-partitioned target table if the source table is a Db2 range-partitioned table and the target table does not exist when creating a Q Subscription.