../E41084-03.epub /> ../E41084-03.mobi />
In an Oracle Automatic Storage Management (Oracle ASM) cluster, a user authenticated
SYSASM can use this clause to remove a user from the password file that is local to the Oracle ASM instance of the current node.
When you drop a user, Oracle Database also purges all of that user's schema objects from the recycle bin.
Caution:Do not attempt to drop the users
SYSTEM. Doing so will corrupt your database.
You must have the
USER system privilege. In an Oracle ASM cluster, you must be authenticated
Specify the user to be dropped. Oracle Database does not drop users whose schemas contain objects unless you specify
CASCADE or unless you first explicitly drop the user's objects.
You cannot drop a user whose schema contains a table that uses a flashback data archive for historical tracking. You must first disable the table's use of the flashback data archive.
CASCADE to drop all objects in the user's schema before dropping the user. You must specify this clause to drop a user whose schema contains any objects.
If the user's schema contains tables, then Oracle Database drops the tables and automatically drops any referential integrity constraints on tables in other schemas that refer to primary and unique keys on these tables.
If this clause results in tables being dropped, then the database also drops all domain indexes created on columns of those tables and invokes appropriate drop routines.
See Also:Oracle Database Data Cartridge Developer's Guide for more information on these routines
Oracle Database invalidates, but does not drop, the following objects in other schemas:
Views or synonyms for objects in the dropped user's schema
Stored procedures, functions, or packages that query objects in the dropped user's schema
Oracle Database does not drop materialized views in other schemas that are based on tables in the dropped user's schema. However, because the base tables no longer exist, the materialized views in the other schemas can no longer be refreshed.
Oracle Database drops all triggers in the user's schema.
Oracle Database does not drop roles created by the user.
You cannot drop a user whose schema contains a table that uses a flashback data archive. You must first disable use of the flashback data archive.