Some operations cannot be performed for VCI extensions and VCI itself.

This section describes SQL commands that cannot be executed for the VCI extensions and VCI itself, and client application commands.

• Operations that cannot be performed for the VCI extension

  Command	Subcommand	Description
  ALTER EXTENSION	UPDATE	The VCI extension cannot be specified. This operation is not required for VCI.
  	SET SCHEMA
  	ADD
  	DROP
  CREATE EXTENSION	SCHEMA	The subcommands on the left cannot be performed if the VCI extension is specified, except when the public schema is specified. This operation is not required for VCI.

• Operations that cannot be performed on relations containing a VCI

  Command	Subcommand	Description
  ALTER INDEX	SET	The subcommands on the left cannot be performed if a VCI is specified. If the operation is required, delete the VCI using DROP INDEX, and re-create it using CREATE INDEX after completing the operation.
  	SET TABLESPACE
  	ALL IN TABLESPACE
  ALTER OPERATOR CLASS	RENAME TO	The subcommands on the left cannot be performed if a VCI is specified. This operation is not supported in VCI.
  	OWNER TO
  	SET SCHEMA
  ALTER OPERATOR FAMILY	ADD
  	DROP
  	RENAME TO
  	OWNER TO
  	SET SCHEMA
  ALTER TABLE	ALL IN TABLESPACE name [ OWNED BY roleName ] SET TABLESPACE newTablespace	A tablespace that contains a VCI cannot be specified. If the operation is required, delete the VCI using DROP INDEX, and re-create it using CREATE INDEX after completing the operation.
  	DROP [ COLUMN ] [ IF EXISTS ] colName [ RESTRICT | CASCADE ]	A column that contains a VCI cannot be specified. If the operation is required, delete the VCI using DROP INDEX, and re-create it using CREATE INDEX after completing the operation.
  	ALTER [ COLUMN ] colName [ SET DATA ] TYPE dataType [ COLLATE collation ] [ USING expr ]
  	CLUSTER ON indexName	A VCI cannot be specified. This operation is not supported in VCI.
  	REPLICA IDENTITY {DEFAULT | USING INDEX indexName | FULL | NOTHING}
  CLUSTER	-	A table that contains a VCI and VCI cannot be specified. If the operation is required, delete the VCI using DROP INDEX, and re-create it using CREATE INDEX after completing the operation.
  CREATE INDEX	UNIQUE	The subcommands on the left cannot be performed if a VCI is specified. This operation is not supported in VCI.
  	CONCURRENTLY
  	[ ASC | DESC ]
  	[ NULLS { FIRST | LAST } ]
  	WITH
  	WHERE
  	INCLUDE
  CREATE OPERATOR CLASS	-	A VCI cannot be specified. This operation is not supported in VCI.
  CREATE OPERATOR FAMILY	-
  CREATE TABLE	EXCLUDE
  DROP INDEX	CONCURRENTLY	The subcommands on the left cannot be performed if a VCI is specified. This operation is not supported in VCI.
  REINDEX	-	A VCI cannot be specified. This command is not required as VCI uses daemon's automatic maintenance to prevent disk space from increasing.

• Operations that cannot be performed on relations containing a VCI

  Command	Description
  clusterdb	Clustering cannot be performed for tables that contain a VCI.
  reindexdb	VCIs cannot be specified on the --index option.