The drop_constraint_clause lets you drop an integrity constraint from the database. Oracle stops enforcing the constraint and removes it from the data dictionary. You can specify only one constraint for each drop_constraint_clause, but you can specify multiple drop_constraint_clauses in one statement.
PRIMARY KEY
Specify PRIMARY KEY to drop the table's primary key constraint.
UNIQUE
Specify UNIQUE to drop the unique constraint on the specified columns.
--------------------------------------------------------------------------------
Note:
If you drop the primary key or unique constraint from a column on which a bitmap join index is defined, then Oracle invalidates the index. See CREATE INDEX for information on bitmap join indexes.
--------------------------------------------------------------------------------
CONSTRAINT
Specify CONSTRAINT constraint to drop an integrity constraint other than a primary key or unique constraint.
CASCADE
Specify CASCADE if you want all other integrity constraints that depend on the dropped integrity constraint to be dropped as well.
KEEP | DROP INDEX
Specify KEEP or DROP INDEX to indicate whether Oracle should preserve or drop the index it has been using to enforce the PRIMARY KEY or UNIQUE constraint.
Restrictions on Dropping Constraints
You cannot drop a primary key or unique key constraint that is part of a referential integrity constraint without also dropping the foreign key. To drop the referenced key and the foreign key together, use the CASCADE clause. If you omit CASCADE, then Oracle does not drop the primary key or unique constraint if any foreign key references it.
You cannot drop a primary key constraint (even with the CASCADE clause) on a table that uses the primary key as its object identifier (OID).
If you drop a referential integrity constraint on a REF column, then the REF column remains scoped to the referenced table.
You cannot drop the scope of the column.
hth
Sy UK