When you drop a cluster, any tables in the recycle bin that were once part of that cluster are purged from the recycle bin and can no longer be recovered with a
FLASHBACK TABLE operation.
You cannot uncluster an individual table. Instead you must perform these steps:
Create a new table with the same structure and contents as the old one, but with no
Drop the old table.
RENAMEstatement to give the new table the name of the old one.
Grant privileges on the new unclustered table. Grants on the old clustered table do not apply.
The cluster must be in your own schema or you must have the
CLUSTER system privilege.
Specify the schema containing the cluster. If you omit
schema, then the database assumes the cluster is in your own schema.
Specify the name of the cluster to be dropped. Dropping a cluster also drops the cluster index and returns all cluster space, including data blocks for the index, to the appropriate tablespace(s).
CONSTRAINTS to drop all referential integrity constraints from tables outside the cluster that refer to primary and unique keys in tables of the cluster. If you omit this clause and such referential integrity constraints exist, then the database returns an error and does not drop the cluster.
Dropping a Cluster: Examples
The following examples drop the clusters created in the "Examples" section of
The following statements drops the
DROP CLUSTER language;
The following statement drops the
personnel cluster as well as tables
dept_20 and any referential integrity constraints that refer to primary or unique keys in those tables:
DROP CLUSTER personnel INCLUDING TABLES CASCADE CONSTRAINTS;