Migration Effects On Users' Old Database Schemas - Oracle Database B10772-01 Administrator's Manual

Introduction to the User Migration Utility
Which Interface Table Column Values Can Be Modified between Phase One and
Phase Two?
After running phase one of the utility, if necessary, enterprise user administrators
can change the interface table columns that are listed in
Table G–2 Interface Table Column Values That Can Be Modified between Phase One and Phase Two
Column Name
USERDN
USERDN_EXIST_FLAG
DBPASSWORD_EXIST_
FLAG
SHARED_SCHEMA
MAPPING_TYPE
MAPPING_LEVEL
CASCADE_FLAG
PHASE_COMPLETED

Migration Effects on Users' Old Database Schemas

If shared schema mapping is not used, then users retain their old database schemas.
If shared schema mapping is used, then users' local schemas are dropped from the
database and they are mapped to a shared schema that the enterprise user
administrator creates for this purpose before performing the migration. When
migrated users own database objects in their old local database schemas,
administrators can specify that the schema and objects are not to be dropped by
setting the CASCADE parameter to NO. When the CASCADE parameter is set to NO,
users who own database objects in their old local schemas do not migrate
successfully so their objects are not dropped.
G-6 Oracle Database Advanced Security Administrator's Guide
Valid Values
DN of user
T/F
T/F
Shared schema name
DB/DOMAIN
ENTRY/SUBTREE
T/F
ZERO/ONE/TWO
Restrictions
If this value is changed, then the administrator should verify
that the USERDN_EXIST_FLAG and the DBPASSWORD_
EXIST_FLAG values are set accordingly.
If the USERDN column value changes, then this column value
should also change to reflect the new USERDN status.
If the USERDN column value changes, then this column value
should also change to reflect whether a database password
exists for the new USERDN.
Specify only if a shared schema exists in the database.
Set this value only if SHARED_SCHEMA is not set to NULL.
Set this value only if SHARED_SCHEMA is not set to NULL.
Set this value only if SHARED_SCHEMA is not set to NULL. If
this column is set to true (T), then the users' schema objects
are forcibly deleted. If this column is set to false (F), then the
administrator must delete all user schema objects before
running phase two.
If the administrator can resolve the conflicts or ambiguities
that are specified with the NEEDS_ATTENTION_FLAG, then
this column value can be changed to ONE so phase two can
be run with the utility.
Table G–2.