User Migration Utility Usage Examples; Migrating Users While Retaining Their Own Schemas - Oracle Database B10772-01 Administrator's Manual

User Migration Utility Usage Examples

Description:
Restrictions:
User Migration Utility Usage Examples
The following sections contain examples of the syntax for some typical uses of this
utility.

Migrating Users While Retaining Their Own Schemas

To migrate users while retaining their old database schemas, set the MAPSCHEMA
parameter to PRIVATE, which is the default setting. For example, to migrate users
scott1, scott2, and all external database users, while retaining their old
schemas, to the directory at c=Users, c=us with the newly generated database
and directory passwords, the syntax shown in
Example 13–2 Migrating Users with MAPSCHEMA=PRIVATE (Default)
umu PHASE=ONE
umu PHASE=TWO
After phase one completes successfully, the interface table is populated with the
user migration information. Then the enterprise user administrator can review the
table to confirm its contents. Because no value was specified for the MAPSCHEMA
G-20 Oracle Database Advanced Security Administrator's Guide
Specifies a text file which contains a list of these parameters
that are intended to be used in a user migration. Each
parameter must be listed on a separate line in the file. If a
parameter is specified in both the parameter file and on the
command line, then the one specified on the command line
takes precedence.
None
DBLOCATION=machine1:1521:ora_sid
DBADMIN=system:manager
USERS=ALL_EXTERNAL:LIST
USERSLIST=scott1:scott2
DIRLOCATION=machine2:636
CONTEXT="c=Users,c=us"
ENTADMIN="cn=janeadmin":welcome
DBLOCATION=machine1:1521:ora_sid
DBADMIN=system:manager
DIRLOCATION=machine2:636
ENTADMIN="cn=janeadmin":welcome
Example 13–2 is used.