Oracle Database Advanced Security 10g Release 1, Administrator'S Manual

Page: 470 / 518

User Migration Utility Usage Examples
G-24 Oracle Database Advanced Security Administrator's Guide
Example G–3 Migrating Users with Shared Schema Mapping Using the MAPTYPE
Parameter
umu PHASE=ONE
DBLOCATION=machine1:1521:ora_sid
DBADMIN=system:manager
USERS=ALL_EXTERNAL:LIST
USERSLIST=scott1:scott2
MAPSCHEMA=SHARED:schema_32
MAPTYPE=DOMAIN:ENTRY
DIRLOCATION=machine2:636
CONTEXT="c=Users, c=us"
ENTADMIN="cn=janeadmin":welcome
umu PHASE=TWO
DBLOCATION=machine1:1521:ora_sid
DBADMIN=system:manager
DIRLOCATION=machine2:636
ENTADMIN="cn=janeadmin":welcome
About Using the SUBTREE Mapping Level Option If a user (
scott
, for example) who is
being migrated will have future user entries in a subtree under it, then it makes
sense to create a subtree level mapping from this user entry (
cn=scott
) to a
schema. However, the database does not interpret the user to be in the subtree so
the mapping does not apply to
scott
himself. For example, if you are migrating
the user
scott
with the DN
cn=scott,o=acme
, and you choose
SUBTREE
as the
mapping level when you run the utility, then a new mapping is created from
cn=scott,o=acme
to the shared schema, but the user
scott
is not mapped to
that schema. Only new users who are created under the
scott
directory entry are
mapped to the shared schema. Consequently, the
SUBTREE
mapping level should
only be specified when user directory entries are placed under other user directory
entries, which would be an unusual directory configuration.
If you want an arbitrary subtree user to be mapped to a single shared schema with
only one mapping entry, then you must use Enterprise Security Manager to create
that mapping.
See Also:
"Managing Enterprise Domain Database Schema
Mappings" on page 13-20 for information about using Enterprise
Security Manager.