Corporation Network Router User Manual

User Migration Utility Usage Examples
G-22 Oracle Database Advanced Security Administrator's Guide
Mapping Users to a Shared Schema Using Different CASCADE Options
The CASCADE parameter setting determines whether users' old database schemas
are automatically dropped when mapping to a shared schema during migration.
CASCADE can be used only when MAPSCHEMA is set to SHARED.
Mapping Users to a Shared Schema with CASCADE=NO
By default, the CASCADE parameter is set to NO. This setting means that when
mapping migrating users to a shared schema, users who own database objects in
their old schemas are not migrated. For users who do not own database objects,
their old database schemas are automatically dropped and they are mapped to the
new shared schema.
Mapping Users to a Shared Schema with CASCADE=YES
If it is known that no migrating users own database objects or want to retain the
objects that they own in their old database schemas, then setting the CASCADE
parameter to YES automatically drops all users' schemas and schema objects and
maps them to the new shared schema. Example G–2 shows the syntax to use when
setting CASCADE to YES. In this example, users scott1, scott2, and all external
database users are migrated to the directory at c=Users, c=us, while mapping all
migrating users to a new shared schema in the database.
Example G–2 Migrating Users with Shared Schema Mapping and CASCADE=YES
umu PHASE=ONE
DBLOCATION=machine1:1521:ora_sid
DBADMIN=system:manager
USERS=ALL_EXTERNAL:LIST
USERSLIST=scott1:scott2
MAPSCHEMA=SHARED:schema_32
CASCADE=YES
DIRLOCATION=machine2:636
CONTEXT="c=Users, c=us"
ENTADMIN="cn=janeadmin":welcome
umu PHASE=TWO
DBLOCATION=machine1:1521:ora_sid
See Also: Example G–1 on page G-21 for a syntax example to
map users to a shared schema with CASCADE set to NO. Note that
because NO is the default setting for CASCADE this parameter does
not have to be specified in the utility command syntax.