Operation Instant In Place Rebuilds Table Permits Concurrent DML Only Modifies Metadata Renaming a general tablespace No Yes No Yes Yes Enabling or disabling general tablespace encryption No Yes No Yes No Enabling or disabling file- per-table tablespace encryption No No Yes No No 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. The following table provides an overview of online DDL support for tablespace operations. For details, see Syntax and Usage Notes. Online DDL Operations Tablespace Operations Syntax and Usage Notes Table 15.22 Online DDL Support for Tablespace Operations •Renaming a general tablespace •Enabling or disabling general tablespace encryption •Enabling or disabling file-per-table tablespace encryption Partitioning Operations ALTER TABLESPACE ... RENAME TO  uses the  INPLACE  algorithm but does not support the ALGORITHM  clause. ALTER TABLESPACE ... ENCRYPTION  uses the  INPLACE  algorithm but does not support the ALGORITHM  clause. For related information, see Section 15.13, “InnoDB Data-at-Rest Encryption” . 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. 3187 ALTER TABLE  tbl_name  ENCRYPTION=’Y’, ALGORITHM=COPY; ALTER TABLESPACE  tablespace_name  ENCRYPTION=’Y’; ALTER TABLESPACE  tablespace_name  RENAME TO  new_tablespace_name ;