EDITION statement to drop an edition, along with all actual editionable objects it contains. An actual editionable object is an editionable object that has been created or modified in an edition.
See Also:CREATE EDITION for a listing of editionable object types
You must have the
EDITION system privilege, granted either directly or through a role.
When successful, this statement drops the specified edition, including versions of any objects associated with that edition. Versions of the same objects in other editions are not dropped. Objects that are not editionable, or that are editionable but have not been actualized in the current edition, are not dropped.
You must specify
CASCADE if the specified edition contains any actual editionable objects.
This statement is subject to the following conditions and restrictions:
The specified edition cannot have both a parent edition and a child edition.
The specified edition cannot contain any actual editionable objects that are inherited by a child edition, even if you specify
EDITION will fail if you attempt to drop the default edition.
EDITION will fail if you attempt to drop the root edition and the recycle bin contains at least one object that used to be in that edition before it was dropped. Under these circumstances, even
CASCADE will fail. In this case, you can purge all objects from the recycle bin with the
DBA_RECYCLEBIN statement and then drop the edition. Refer to PURGE for more information.
EDITION will also fail if you attempt to drop the leaf edition and the recycle bin contains at least one object that used to be in that edition before it was dropped. However, under these circumstances,
CASCADE will succeed.
The only type of editioned object that might be in the recycle bin is a trigger.
For examples that use this statement, refer to CREATE EDITION.