User's Manual

Introduction to the User Migration Utility
Using the User Migration Utility G-7
If some users want to retain the objects in their local database schemas and be
mapped to a shared schema, then the administrator can manually migrate those
objects to the shared schema before performing the bulk user migration. However,
when objects are migrated to a shared schema, they are shared among all users who
share that new schema.
Table G–3 summarizes the effects of setting the MAPSCHEMA and CASCADE
parameters.
Migration Process
Enterprise users, those that are defined and managed in the directory, can be
authenticated to the database either with a password or with a certificate. Users that
authenticate with a password require an Oracle database password, which is stored
in the directory. Users that authenticate with a certificate must have a valid X.509 v3
certificate.
This utility performs the following steps during migration:
1. Selects the users from the database for migration.
2. Creates corresponding user entries or uses existing entries in the directory.
3. Creates new database passwords and copies the corresponding verifiers to the
directory for migrating users.
4. Puts the schema mapping information for the migrating users' entries in the
directory. (optional)
Table G–3 Effects of Choosing Shared Schema Mapping with CASCADE Options
MAPSCHEMA
Parameter Setting
CASCADE
Parameter Setting
User Migration
Successful?
User Schema
Objects Dropped?
PRIVATE NO (default setting) Yes No
SHARED NO
Yes
1
1
Users migrate successfully only if they do not own objects in their old database schemas; otherwise, they fail.
No
SHARED YES
Yes
2
2
Users migrate successfully and their old database schemas are dropped.
Yes
See Also: "User Migration Utility Parameters" on page G-12 for
detailed information about the MAPSCHEMA, CASCADE, and other
parameters that can be used with this utility.