This topic describes the conversion scope of CREATE TABLE DDL operations during data migration from an Oracle database to an Oracle tenant of OceanBase Database.
Syntax
CREATE [table_prefix_options]
TABLE
[schema_name. ] table_name
[ SHARING = {sharing_options} ]
{table_definition_options}
[ MEMOPTIMIZE FOR READ ][ MEMOPTIMIZE FOR WRITE ][ PARENT [ schema_name. ] table_name ];
table_definition_options
{ relational_table | object_table | XMLType_table }
Creating relational tables is supported. For more information, see Create a relational table.
Creating object tables and XML tables (option: object_table or XMLType_table) is not supported. The conversion generates an empty statement.
Example 1:
CREATE TYPE employees_typ AS OBJECT (e_no NUMBER, e_address CHAR(30)); CREATE TABLE employees_obj_t OF employees_typ (e_no PRIMARY KEY) OBJECT IDENTIFIER IS PRIMARY KEY; CREATE TABLE TABLE_TYPE_2 (d_no NUMBER, mgr_ref REF employees_typ SCOPE IS employees_obj_t);
Example 2:
CREATE TABLE TABLE_TYPE_3 OF XMLTYPE; CREATE TABLE TABLE_TYPE_4 OF XMLTYPE XMLSCHEMA "http://www.example.com/xwarehouses.xsd" ELEMENT "Warehouse"; CREATE TABLE TABLE_TYPE_5 (C1 NUMBER,C2 XMLTYPE) XMLTYPE SPEC STORE AS CLOB (TABLESPACE EXAMPLE STORAGE (INITIAL 6144) CHUNK 4000 NOCACHE LOGGING);
The
table_prefix_options
option is not supported. This option will be ignored. Sample code:[ { GLOBAL | PRIVATE } TEMPORARY | SHARDED | DUPLICATED | [ IMMUTABLE ] BLOCKCHAIN | IMMUTABLE ]
The
sharing_options
option is not supported. This option will be ignored. Sample code:{ METADATA | DATA | EXTENDED DATA | NONE }
The
MEMOPTIMIZE FOR READ
option is not supported. This option will be ignored. Sample code:CREATE TABLE MEMO_1 (C NUMBER) MEMOPTIMIZE FOR READ;
The
MEMOPTIMIZE FOR WRITE
option is not supported. This option will be ignored. Sample code:CREATE TABLE MEMO_2 (C NUMBER) MEMOPTIMIZE FOR WRITE;
The
PARENT [ schema_name. ] table
option is not supported. This option will be ignored. Sample code:CREATE SHARDED TABLE PARENT_1 (C NUMBER) PARENT PARENT_F;