This topic describes the scenarios where CREATE TABLE DDL operations performed in an Oracle database can be converted by the DDL synchronization component of the data transmission service but cannot be performed in an Oracle tenant of OceanBase Database during data migration from the Oracle database to the Oracle tenant of OceanBase Database.
Both the SUBPARTITION TEMPLATE and SUBPARTITION subpartition_name VALUES (int) clauses exist in the CREATE TABLE DDL statement
Take note of the following items on the support for executing a CREATE TABLE DDL statement that has both the SUBPARTITION TEMPLATE and SUBPARTITION subpartition_name VALUES (int) clauses to create subpartitions:
Supported in an Oracle database.
Not supported in an Oracle tenant of OceanBase Database.
Here is an example:
CREATE TABLE SMNOTIFY
("REGION" NUMBER(4,0) NOT NULL ENABLE,
"INTIME" DATE DEFAULT sysdate NOT NULL ENABLE)
PARTITION BY RANGE ("INTIME")
SUBPARTITION BY LIST ("REGION")
SUBPARTITION TEMPLATE (
SUBPARTITION "L_23" VALUES (100))
(PARTITION "P_R_202208" VALUES LESS THAN (TO_DATE(' 2022-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
)(SUBPARTITION sp0 VALUES (10)),
PARTITION "P_R_202209" VALUES LESS THAN (TO_DATE(' 2022-10-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
(SUBPARTITION sp2 VALUES (20)),
PARTITION "P_R_PMAX" VALUES LESS THAN (TO_DATE(' 2038-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
(SUBPARTITION sp4 VALUES (30)));