OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

OceanBase Database

SQL - V3.2.4Enterprise Edition

    Download PDF

    OceanBase logo

    The Unified Distributed Database for the AI Era.

    Follow Us
    Products
    OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
    Resources
    DocsBlogLive DemosTraining & Certification
    Company
    About OceanBaseTrust CenterLegalPartnerContact Us
    Follow Us

    © OceanBase 2026. All rights reserved

    Cloud Service AgreementPrivacy PolicySecurity
    Contact Us
    Document Feedback
    1. Documentation Center
    2. OceanBase Database
    3. SQL
    4. V3.2.4
    iconOceanBase Database
    SQL - V 3.2.4Enterprise Edition
    SQL
    KV
    • V 4.4.2
    • V 4.3.5
    • V 4.3.3
    • V 4.3.1
    • V 4.3.0
    • V 4.2.5
    • V 4.2.2
    • V 4.2.1
    • V 4.2.0
    • V 4.1.0
    • V 4.0.0
    • V 3.1.4 and earlier

    ALTER TABLE

    Last Updated:2023-10-24 09:23:03  Updated
    share
    What is on this page
    Purpose
    Syntax
    Parameters
    Examples
    Examples of adding and dropping columns
    Index operations
    Example of partitions
    Example of DOP

    folded

    share

    Purpose

    You can use this statement to modify the structure of an existing table. For example, you can use this statement to modify a table and its attributes, add columns to it, modify its columns and attributes, and delete its columns.

    Syntax

    alter_table_stmt:
          ALTER TABLE table_name alter_table_action_list;
    
    alter_table_action_list:
        alter_table_action [, alter_table_action ...]
    
    alter_table_action: 
          ADD [COLUMN] column_definition  
              [FIRST | AFTER column_name]
        | ADD [COLUMN] (column_definition_list)
        | ADD [CONSTRAINT [constraint_name]] UNIQUE {INDEX | KEY} 
              [index_name] index_desc
        | ADD [CONSTRAINT [constraint_name]] FOREIGN KEY
              [index_name] index_desc
              REFERENCES reference_definition
              [match_action][opt_reference_option_list]
        | ADD {INDEX | KEY} 
              [index_name] index_desc
        | ADD PARTITION (range_partition_list)
        | ALTER [COLUMN] column_name {
              SET DEFAULT const_value 
            | DROP DEFAULT
          }
        | ALTER INDEX index_name 
              [VISIBLE | INVISIBLE]
        | CHANGE [COLUMN] column_name column_definition
        | DROP [COLUMN] column_name
        | DROP {INDEX | KEY} index_name
        | DROP {PARTITION | SUBPARTITION} partition_name_list
        | DROP TABLEGROUP
        | DROP FOREIGN KEY fk_name
        | MODIFY [COLUMN] column_definition
        | RENAME [TO] table_name
        | RENAME {INDEX | KEY} old_index_name TO new_index_name
        | REORGANIZE PARTITION name_list INTO partition_range_or_list
        | [SET] table_option_list
        | TRUNCATE {PARTITION | SUBPARTITION} partition_name_list
    
    column_definition_list:
        column_definition [, column_definition ...]
    
    column_definition:
        column_name data_type
        [DEFAULT const_value] [AUTO_INCREMENT]
        [NULL | NOT NULL] [[PRIMARY] KEY] [UNIQUE [KEY]] comment
    
    index_desc:
       (column_desc_list) [index_type] [index_option_list]
    
    match_action:
       MATCH {SIMPLE | FULL | PARTIAL}
    
    opt_reference_option_list:
       reference_option [,reference_option...]
    
    reference_option:
       ON {DELETE | UPDATE} {RESTRICT | CASCADE | SET NULLX | NO ACTION | SET DEFAULT}
    
    column_desc_list:
        column_desc [, column_desc ...]
    
    column_desc:
         column_name [(length)] [ASC | DESC]
    
    index_type:
        USING BTREE
    
    index_option_list:
        index_option [ index_option ...]
    
    index_option:
          [GLOBAL | LOCAL]
        | block_size
        | compression
        | STORING(column_name_list)
        | comment
    
    table_option_list:
        table_option [ table_option ...]
    
    table_option:
        | primary_zone
        | table_tablegroup
        | block_size
        | compression
        | AUTO_INCREMENT [=] INT_VALUE
        | comment
        | DUPLICATE_SCOPE [=] "none|zone|region|cluster"
        | parallel_clause
    
    parallel_clause:
        {NOPARALLEL | PARALLEL integer}
    
    partition_option:
          PARTITION BY HASH(expression)
          [subpartition_option] PARTITIONS partition_count
        | PARTITION BY KEY([column_name_list])
          [subpartition_option] PARTITIONS partition_count
        | PARTITION BY RANGE {(expression) | COLUMNS (column_name_list)}
          [subpartition_option] (range_partition_list)
    
    subpartition_option:
          SUBPARTITION BY HASH(expression)
          SUBPARTITIONS subpartition_count
        | SUBPARTITION BY KEY(column_name_list)
          SUBPARTITIONS subpartition_count
        | SUBPARTITION BY RANGE {(expression) | COLUMNS (column_name_list)}
          (range_subpartition_list)
    
    range_partition_list:
        range_partition [, range_partition ...]
    
    range_partition:
        PARTITION partition_name
        VALUES LESS THAN {(expression_list) | MAXVALUE}
    
    range_subpartition_list:
        range_subpartition [, range_subpartition ...]
    
    range_subpartition:
        SUBPARTITION subpartition_name
        VALUES LESS THAN {(expression_list) | MAXVALUE}
    
    expression_list:
        expression [, expression ...]
    
    column_name_list:
        column_name [, column_name ...]
    
    partition_name_list:
        partition_name [, partition_name ...]
    
    partition_count | subpartition_count:
        INT_VALUE
    

    Parameters

    Parameter Description
    ADD [COLUMN] Adds columns. You can add generated columns.
    Note
    You cannot add primary key columns for the moment.
    [FIRST | AFTER column_name] Specifies the added column as the first column of the table or to be after the column_name column. Currently, OceanBase Database allows you to specify the position of a column only in the ADD COLUMN syntax.
    CHANGE [COLUMN] Modifies column names and definitions.
    MODIFY [COLUMN] Modifies the column attribute.
    ALTER [COLUMN] {SET DEFAULT const_value | DROP DEFAULT} Changes the default value of a column.
    DROP [COLUMN] Drops a column. You cannot drop a primary key column or columns that contain indexes.
    ADD UNIQUE {INDEX | KEY} Adds a unique index. When you create a unique index, the constraint of the same name as the index is also added to the table.
    • If you do not specify the key name, the name specified for the index is used. If you do not specify the index name, the index is named based on the index naming rule.
    • If you do not specify the index name, the name specified for the key is used. If you do not specify the key name, the index name is a combination of an underscore (_) and a sequence number. For example, an index created on the column c1 is named c1_2 if a duplicate name exists.
    • If you specify both the key name and index name, the index name is used as the key name and index name. You can execute the SHOW INDEX statement to view the indexes of a table.
    ADD FOREIGN KEY Adds a foreign key. If you do not specify the foreign key name, the foreign key name is a combination of the table name, OBFK, and the creation time. For example, the name of the foreign key created for the table t1 at 00:00:00 on August 1, 2021 is t1_OBFK_1627747200000000.
    ADD {INDEX | KEY} Adds a normal index. INDEX and KEY are synonymous. If you do not specify the index name, the name of the first column referenced by the index is used as the index name. If a duplicate index name exists, the index name is a combination of an underscore (_) and a sequence number. For example, an index created on the column c1 is named c1_2 if a duplicate name exists. You can execute the SHOW INDEX statement to view the indexes of a table.
    ALTER INDEX Specifies whether an index is visible. The SQL optimizer will not select an index whose status is INVISIBLE.
    ADD [PARTITION] Adds a partition to a partitioned table. OceanBase Database does not support converting a non-partitioned table to a partitioned table.
    DROP {PARTITION | SUBPARTITION} Drops partitions:
    • PARTITION: drops the specified RANGE or LIST partitions, as well as all subpartitions that exist under these partitions. The partition definitions and partition data are also deleted, but the indexes defined on the partitioned table are maintained.
    • SUBPARTITION: drops the specified *-RANGE or *-LIST subpartitions, including the subpartition definitions and subpartition data, and maintains the indexes defined on the partitioned table. Separate multiple partition names with commas (,).

    Notice
    Before you drop a partition, ensure that no active transactions or queries exist in this partition. Otherwise, SQL statement errors or exceptions may occur.
    REORGANIZE [PARTITION] Reorganizes a partition.
    Note
    The current version does not support this parameter.
    TRUNCATE {PARTITION | SUBPARTITION} Truncates partitions:
    • PARTITION: deletes all data in the specified RANGE or LIST partitions, as well as data in all subpartitions that exist under these partitions, and maintains the indexes defined on the partitioned table.
    • SUBPARTITION: deletes all data in the specified *-RANGE or *-LIST subpartitions, and maintains the indexes defined on the partitioned table. Separate multiple partition names with commas (,).

    Notice
    Before you delete partition data, ensure that no active transactions or queries exist in this partition. Otherwise, SQL statement errors or exceptions may occur.
    RENAME [TO] table_name Renames a table.
    RENAME {INDEX | KEY} Renames an index or a key.
    DROP [TABLEGROUP] Drops a table group.
    DROP [FOREIGN KEY] Drops an external key.
    [SET] table_option Sets table attributes. The following parameters are supported:
    • PRIMARY_ZONE: sets the primary zone of the table.
    • REPLICA_NUM: sets the number of replicas of the table (not supported).
    • TABLE_GROUP: sets the group to which the table belongs.
    • BLOCK_SIZE: sets the microblock size of the table. Default Value: 16384, which is 16 KB. Value range: [1024, 1048576].
    • COMPRESSION: sets the compression mode of the table. Default value: None, which means that data is not compressed.
    • AUTO_INCREMENT: sets the next value of the auto-increment column in the table.
    • comment: sets the comments for the table.
    • DUPLICATE_SCOPE: sets the replication mode for the table.
    • PROGRESSIVE_MERGE_NUM: sets the number of progressive compaction steps. Value range: [1, 64].
    • parallel_clause: specifies the degree of parallelism (DOP) at the table level.
    • NOPARALLEL: sets the DOP to 1, which is the default value.
    • PARALLEL integer: sets the DOP to an integer greater than or equal to 1.

    Examples

    Examples of adding and dropping columns

    Create a table named tbl1 and execute the DESCRIBE statement to view the table information.

    obclient> CREATE TABLE tbl1 (c1 INT(11) PRIMARY KEY,c2 VARCHAR(50)); 
    Query OK, 0 rows affected
    
    obclient> DESCRIBE tbl1; 
    +-------+------------+----------+--------+---------+-------+
    | Field | Type       | Null     | Key    | Default | Extra | 
    +-------+------------+----------+--------+---------+-------+
    | c1    | int(11)    | NO       | PRI    | NULL    |       |    
    | c2    | varchar(50)| YES      |        | NULL    |       |   
    +-------+------------+----------+--------+---------+-------+
    
    • Add a column named c3 and execute the DESCRIBE statement to view the table information.

      obclient> ALTER TABLE tbl1 ADD c3 INTEGER;
      Query OK, 1 row affected
      
      obclient> DESCRIBE tbl1; 
      +-------+------------+----------+--------+---------+-------+
      | Field | Type       | Null | Key | Default | Extra | 
      +-------+------------+----------+--------+---------+-------+
      | c1    | int(11)    | NO       | PRI    | NULL    |       |    
      | c2    | varchar(50)| YES      |        | NULL    |       |  
      | c3    | int(11)    | YES      |        | NULL    |       |  
      +-------+------------+----------+--------+---------+-------+
      3 row affected
      
    • Drop the c3 column and execute the DESCRIBE statement to view the table information.

      obclient> ALTER TABLE tbl1 DROP c3;
      Query OK, 1 row affected
      
      obclient> DESCRIBE tbl1; 
      +-------+------------+----------+--------+---------+-------+
      | Field | Type       | Null | Key | Default | Extra | 
      +-------+------------+----------+--------+---------+-------+
      | c1    | int(11)    | NO       | PRI    | NULL    |       |    
      | c2    | varchar(50)| YES      |        | NULL    |       |  
      +-------+------------+----------+--------+---------+-------+
      2 row affected
      
    • Rename the c2 column in the tbl1 table to c3 and execute the DESCRIBE statement to view the table information.

      obclient> ALTER TABLE tbl1 CHANGE COLUMN c2 c3 VARCHAR(50);
      Query OK, 1 row affected
      
      obclient> DESCRIBE tbl1; 
      +-------+------------+----------+--------+---------+-------+
      | Field | Type       | Null | Key | Default | Extra | 
      +-------+------------+----------+--------+---------+-------+
      | c1    | int(11)    | NO       | PRI    | NULL    |       |    
      | c3    | varchar(50)| YES      |        | NULL    |       |  
      +-------+------------+----------+--------+---------+-------+
      2 rows affected
      
    • Add a column named c4 to the tbl1 table, set this column as the first column of the table, and execute the DESCRIBE statement to view the table information.

      obclient> ALTER TABLE tbl1 ADD COLUMN c4 INTEGER FIRST;
      Query OK, 1 row affected
      
      obclient> DESCRIBE tbl1; 
      +-------+------------+----------+--------+---------+-------+
      | Field | Type       | Null | Key | Default | Extra | 
      +-------+------------+----------+--------+---------+-------+
      | c4    | int(11)    | YES      |        | NULL    |       |  
      | c1    | int(11)    | NO       | PRI    | NULL    |       |    
      | c3    | varchar(50)| YES      |        | NULL    |       |  
      +-------+------------+----------+--------+---------+-------+
      3 row affected
      
    • Add a column named c2 behind the c1 column and execute the DESCRIBE statement to view the table information.

      obclient> ALTER TABLE tbl1 ADD COLUMN c2 INTEGER AFTER c1;
      Query OK, 1 row affected
      
      obclient> DESCRIBE tbl1; 
      +-------+------------+----------+--------+---------+-------+
      | Field | Type       | Null     | Key    | Default | Extra | 
      +-------+------------+----------+--------+---------+-------+
      | c4    | int(11)    | YES      |        | NULL    |       |  
      | c1    | int(11)    | NO       | PRI    | NULL    |       | 
      | c2    | int(11)    | YES      |        | NULL    |       |    
      | c3    | varchar(50)| YES      |        | NULL    |       |  
      +-------+------------+----------+--------+---------+-------+
      4 row affected
      
    • Add a column named c5 before the c4 column and execute the DESCRIBE statement to view the table information.

      obclient> ALTER TABLE tbl1 ADD COLUMN c5 INTEGER BEFORE c4;
      Query OK, 1 row affected
      
      obclient> DESCRIBE tbl1; 
      +-------+------------+----------+--------+---------+-------+
      | Field | Type       | Null     | Key    | Default | Extra | 
      +-------+------------+----------+--------+---------+-------+
      | c5    | int(11)    | YES      |        | NULL    |       |  
      | c4    | int(11)    | YES      |        | NULL    |       |  
      | c1    | int(11)    | NO       | PRI    | NULL    |       | 
      | c2    | int(11)    | YES      |        | NULL    |       |    
      | c3    | varchar(50)| YES      |        | NULL    |       |  
      +-------+------------+----------+--------+---------+-------+
      5 row affected
      
    • Add a column named c5 before the c4 column and execute the DESCRIBE statement to view the table information.

      obclient> ALTER TABLE tbl1 ADD COLUMN c5 INTEGER BEFORE c4;
      Query OK, 1 row affected
      
      obclient> DESCRIBE tbl1; 
      +-------+------------+----------+--------+---------+-------+
      | Field | Type       | Null     | Key    | Default | Extra | 
      +-------+------------+----------+--------+---------+-------+
      | c5    | int(11)    | YES      |        | NULL    |       |  
      | c4    | int(11)    | YES      |        | NULL    |       |  
      | c1    | int(11)    | NO       | PRI    | NULL    |       | 
      | c2    | int(11)    | YES      |        | NULL    |       |    
      | c3    | varchar(50)| YES      |        | NULL    |       |  
      +-------+------------+----------+--------+---------+-------+
      5 row affected
      
    • Add a foreign key constraint fk1 to the tbl2 table.

      obclient> CREATE TABLE tbl2(c1 INT(11) PRIMARY KEY,c2 INT(50)); 
      Query OK, 0 row affected
      obclient> CREATE TABLE tbl3(c1 INT(11) PRIMARY KEY,c2 INT(50));
      Query OK, 0 row affected
      obclient> ALTER TABLE tbl2 ADD CONSTRAINT fk1 FOREIGN KEY (c2) REFERENCES tbl3(c1);
      Query OK, 0 row affected
      
    • Drop the foreign key constraint fk1 from the tbl3 table.

      obclient> ALTER TABLE tbl2 DROP FOREIGN KEY fk1;
      Query OK, 0 row affected
      

    Index operations

    • Rename the ind1 index on the tbl2 table to ind2.

      obclient> CREATE TABLE tbl2(c1 INT(11) PRIMARY KEY,c2 INT(50));
      Query OK, 0 row affected
      
      obclient> CREATE INDEX ind1 ON tbl2 (c2 ASC);
      Query OK, 0 row affected
      obclient> ALTER TABLE tbl2 RENAME INDEX ind1 TO ind2;
      Query OK, 0 row affected
      
    • Create an index named ind3 on the tbl2 table to reference the c1 and c2 columns.

      obclient> ALTER TABLE tbl2 ADD INDEX ind3 (c1,c2) USING BTREE;
      Query OK, 0 row affected
      

      You can execute the SHOW INDEX statement to view the created indexes.

      obclient> SHOW INDEX FROM tbl2;
      +-------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+-----------+---------------+---------+
      | Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment   | Index_comment | Visible |
      +-------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+-----------+---------------+---------+
      | tbl2  |          0 | PRIMARY  |            1 | c1          | A         |        NULL | NULL     | NULL   |      | BTREE      | available |               | YES     |
      | tbl2  |          1 | ind2     |            1 | c2          | A         |        NULL | NULL     | NULL   |  YES | BTREE      | available |               | YES     |
      | tbl2  |          1 | ind3     |            1 | c1          | A         |        NULL | NULL     | NULL   |      | BTREE      | available |               | YES     |
      | tbl2  |          1 | ind3     |            2 | c2          | A         |        NULL | NULL     | NULL   |  YES | BTREE      | available |               | YES     |
      +-------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+-----------+---------------+---------+
      4 rows in set
      
    • Drop the ind2 index from the tbl2 table.

      obclient> ALTER TABLE tbl2 DROP INDEX ind2;
      Query OK, 0 row affected
      

    Note

    You can use the preceding method to implement an atomic change to an index in actual O&M scenarios.

    Example of partitions

    • Truncate partitions M202001 and M202002 of the t_log_part_by_range table.

      obclient> CREATE TABLE t_log_part_by_range (
          log_id      bigint NOT NULL 
          , log_value varchar(50)
          , log_date  timestamp NOT NULL  
      ) PARTITION BY RANGE(UNIX_TIMESTAMP(log_date)) 
      (
          PARTITION M202001 VALUES LESS THAN(UNIX_TIMESTAMP('2020/02/01'))
          , PARTITION M202002 VALUES LESS THAN(UNIX_TIMESTAMP('2020/03/01'))
          , PARTITION M202003 VALUES LESS THAN(UNIX_TIMESTAMP('2020/04/01'))
          , PARTITION M202004 VALUES LESS THAN(UNIX_TIMESTAMP('2020/05/01'))
          , PARTITION M202005 VALUES LESS THAN(UNIX_TIMESTAMP('2020/06/01'))
      );
      Query OK, 0 rows affected 
      
      obclient> ALTER TABLE t_log_part_by_range TRUNCATE PARTITION M202001, M202002;
      Query OK, 0 rows affected 
      
    • Add the M202006 partition to the t_log_part_by_range table.

      obclient> CREATE TABLE t_log_part_by_range (
          log_id      bigint NOT NULL 
          , log_value varchar(50)
          , log_date  timestamp NOT NULL  
      ) PARTITION BY RANGE(UNIX_TIMESTAMP(log_date)) 
      (
          PARTITION M202001 VALUES LESS THAN(UNIX_TIMESTAMP('2020/02/01'))
          , PARTITION M202002 VALUES LESS THAN(UNIX_TIMESTAMP('2020/03/01'))
          , PARTITION M202003 VALUES LESS THAN(UNIX_TIMESTAMP('2020/04/01'))
          , PARTITION M202004 VALUES LESS THAN(UNIX_TIMESTAMP('2020/05/01'))
          , PARTITION M202005 VALUES LESS THAN(UNIX_TIMESTAMP('2020/06/01'))
      );
      Query OK, 0 rows affected
      
      obclient> ALTER TABLE t_log_part_by_range ADD PARTITION 
               (PARTITION M202006 VALUES LESS THAN(UNIX_TIMESTAMP('2020/07/01'))
               );
      Query OK, 0 rows affected 
      

    Example of DOP

    Change the DOP of the tbl1 table to 2.

    obclient> ALTER TABLE tbl3 PARALLEL 2;
    Query OK, 0 rows affected
    

    Previous topic

    ALTER SEQUENCE
    Last

    Next topic

    ALTER TABLEGROUP
    Next
    What is on this page
    Purpose
    Syntax
    Parameters
    Examples
    Examples of adding and dropping columns
    Index operations
    Example of partitions
    Example of DOP