content_image/797430.jpg
tables. See Section 13.1.36, “RENAME TABLE Statement” .) Privileges granted specifically for the renamed table are not migrated to the new name. They must be changed manually. 

## Tablespace Operations 

The following table provides an overview of online DDL support for tablespace operations. For details, see Syntax and Usage Notes. 

<img src='content_image/797430.jpg'>

## Syntax and Usage Notes 

•Renaming a general tablespace 

ALTER TABLESPACE tablespace_name  RENAME TO new_tablespace_name ; 

ALTER TABLESPACE ... RENAME TO  uses the INPLACE  algorithm but does not support the ALGORITHM  clause. 

•Enabling or disabling general tablespace encryption 

ALTER TABLESPACE tablespace_name  ENCRYPTION=’Y’; 

ALTER TABLESPACE ... ENCRYPTION  uses the INPLACE  algorithm but does not support the ALGORITHM  clause. 

## Partitioning Operations 

For related information, see Section 15.13, “InnoDB Data-at-Rest Encryption” . 

•Enabling or disabling file-per-table tablespace encryption 

ALTER TABLE tbl_name  ENCRYPTION=’Y’, ALGORITHM=COPY; 

For related information, see Section 15.13, “InnoDB Data-at-Rest Encryption” . 

With the exception of some ALTER TABLE  partitioning clauses, online DDL operations for partitioned InnoDB  tables follow the same rules that apply to regular InnoDB  tables. 

Some ALTER TABLE  partitioning clauses do not go through the same internal online DDL API as regular non-partitioned InnoDB  tables. As a result, online support for ALTER TABLE  partitioning clauses varies. 

